|
Home > Archive > PostgreSQL Discussion > September 2005 > createdb problem
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
|
|
| Sterpu Victor 2005-09-24, 8:23 pm |
| I use postgresql 7.4.8.
I need te delete and recreate a database very ofent, because I do some
tests in it.
After a few months the command createdb becamed very slow.
How can I make it go fast again?
Thank you.
---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
| |
| Tom Lane 2005-09-25, 3:23 am |
| Sterpu Victor <victor@ambra.ro> writes:
> I use postgresql 7.4.8.
> I need te delete and recreate a database very ofent, because I do some
> tests in it.
> After a few months the command createdb becamed very slow.
> How can I make it go fast again?
The only explanation that comes to mind is that you haven't ever
vacuumed pg_database ... at this point you probably need a VACUUM
FULL, and maybe REINDEX too, to get it back down to a reasonable
size.
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 2: Don't 'kill -9' the postmaster
| |
| Jim C. Nasby 2005-09-25, 3:23 am |
| My guess is you need to vacuum. Try a vacuumdb -a.
On Sun, Sep 25, 2005 at 03:46:38AM +0300, Sterpu Victor wrote:
> I use postgresql 7.4.8.
> I need te delete and recreate a database very ofent, because I do some
> tests in it.
> After a few months the command createdb becamed very slow.
>
> How can I make it go fast again?
> Thank you.
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 3: Have you checked our extensive FAQ?
>
> http://www.postgresql.org/docs/faq
>
--
Jim C. Nasby, Sr. Engineering Consultant jnasby@pervasive.com
Pervasive Software http://pervasive.com work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
|
|
|
|
|