On Wed, Oct 22, 2008 at 2:46 AM, Grzegorz Jaśkiewicz <[EMAIL PROTECTED]> wrote:
> what's the version you're running ? you shouldn't run into that problem too
> often with 8.3
I'm running 8.3.3 soon to be 8.3.4 or .5 if there's a bug fix due out.
There's only so much the autovacuum daemon can do w
what's the version you're running ? you shouldn't run into that problem too
often with 8.3
just like guys said here, regular vacuum, and reindex once in a while.
On Tue, Oct 21, 2008 at 10:46 AM, Robert Treat
<[EMAIL PROTECTED]> wrote:
> On Tuesday 21 October 2008 09:00:30 postgres Emanuel CALVO FRANCO wrote:
>> After run VACUUM, you must run REINDEXDB to decrease indexes.
>>
>
> This is probably overkill, as you won't need to do this for a lot of tables in
On Tuesday 21 October 2008 09:00:30 postgres Emanuel CALVO FRANCO wrote:
> After run VACUUM, you must run REINDEXDB to decrease indexes.
>
This is probably overkill, as you won't need to do this for a lot of tables in
your database, and the locking issues are probably unhelpful.
> You can pg_re
On 21/10/2008 11:59, Ruben Blanco wrote:
> My database is growing fast taking too much disk space. How can I free
> disk space without performing a VACCUM FULL? It locks the database for
> several hours, and that is not a solution.
You shouldn't need to do VACUUM FULL - plain VACUUM should do the
On Tue, 2008-10-21 at 11:59 +0100, Ruben Blanco wrote:
> My database is growing fast taking too much disk space.
Are you running regular vacuum?
--
Devrim GÜNDÜZ, RHCE
devrim~gunduz.org, devrim~PostgreSQL.org, devrim.gunduz~linux.org.tr
http://www.gunduz.org
signature.asc
Des
After run VACUUM, you must run REINDEXDB to decrease indexes.
You can pg_resetxlog too, but you need restart server to do that.
2008/10/21 Ruben Blanco <[EMAIL PROTECTED]>:
> Hi:
>
> My database is growing fast taking too much disk space. How can I free disk
> space without performing a VACCUM FU
Hi:
My database is growing fast taking too much disk space. How can I free disk
space without performing a VACCUM FULL? It locks the database for several
hours, and that is not a solution.
I guess a backup-restore would do the work but, isn't there a better way to
do this without shutting down po
