We found the auto vacuum would always kick in during our daily data loads
in the mornings and completely bottle neck our system, and in the end had
to turn it off and schedule our own vacuum analyze over the weekend each
week using crontab. We do a couple of gigs of inserts a week into our
postgre
Out of curiosity, what happens if you dump that database without specifying
a schema - do you get all 708 tables?
On Fri, Jun 22, 2012 at 8:45 PM, Stefan Schwarzer wrote:
> Hi there,
>
> I am pg_dump-ing all tables from schema public on the server
>
> /usr/local/pgsql/bin/pg_dump -U user m
space?
Thanks for any help people can give!
Anthony Bull
Software Architect
m2Wealth International Ltd.
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
About 3 hours after the Vacuum full completed, the disk space got returned
to the OS - now Windows is reporting it has all that disk back. Must have
been waiting for something? Anyway, great news!
On Mon, May 28, 2012 at 11:23 PM, Anthony Bull wrote:
> I did not run analyze, only vacuum f
tables
in the db.
Will analyze help? I was under the impression that was more for statistics
gathering and index optimising?
On Mon, May 28, 2012 at 11:16 PM, Jens Wilke wrote:
> On Montag, 28. Mai 2012, Anthony Bull wrote:
>
> Hi,
>
> >This did not
> > work either - pos
Greetings,
I am having problems reclaiming an excessive amount of disk space used by a
database, running on Windows PostgreSQL v8.3 (unfortunately we are stuck
with this version at the moment).
The database had a 16GB table, that I deleted a lot of data from. After
deleting from this table, I ra
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
