Steven Flatt escribió:
> Most of our large (partitioned) tables are insert-only (truncated
> eventually) so will not be touched by autovacuum until wraparound prevention
> kicks in. However the tables are partitioned by timestamp so tables will
> cross the 1.9 billion marker at different times (s
On 6/25/07, Jim Nasby <[EMAIL PROTECTED]> wrote:
If you set that to 2B, that means you're 2^31-"2 billion"-100
transactions away from a shutdown when autovac finally gets around to
trying to run a wraparound vacuum on a table. If you have any number
of large tables, that could be a big probl
On Jun 21, 2007, at 3:37 PM, Steven Flatt wrote:
Thanks everyone. It appears that we had hacked the 502.pgsql
script for our 8.1 build to disable the daily vacuum. I was not
aware of this when building and upgrading to 8.2.
Much better to change stuff in a config file than to hack installe
Steven Flatt escribió:
> Thanks everyone. It appears that we had hacked the 502.pgsql script for our
> 8.1 build to disable the daily vacuum. I was not aware of this when
> building and upgrading to 8.2.
>
> So it looks like for the past two weeks, that 36 hour db-wide vacuum has
> been running
Thanks everyone. It appears that we had hacked the 502.pgsql script for our
8.1 build to disable the daily vacuum. I was not aware of this when
building and upgrading to 8.2.
So it looks like for the past two weeks, that 36 hour db-wide vacuum has
been running every 24 hours. Good for it for b
In response to "Steven Flatt" <[EMAIL PROTECTED]>:
> On 6/21/07, Francisco Reyes <[EMAIL PROTECTED]> wrote:
> >
> > Are you on FreeBSD by any chance?
> >
> > I think the FreeBSD port by default installs a script that does a daily
> > vacuum.
>
>
> Yes, FreeBSD. Do you know what script that is?
On Thu, 21 Jun 2007, Steven Flatt wrote:
On 6/21/07, Francisco Reyes <[EMAIL PROTECTED]> wrote:
Are you on FreeBSD by any chance?
I think the FreeBSD port by default installs a script that does a daily
vacuum.
Yes, FreeBSD. Do you know what script that is? And it does a db-wide
VACUUM AN
On 6/21/07, Francisco Reyes <[EMAIL PROTECTED]> wrote:
Are you on FreeBSD by any chance?
I think the FreeBSD port by default installs a script that does a daily
vacuum.
Yes, FreeBSD. Do you know what script that is? And it does a db-wide
VACUUM ANALYZE every day?! That is certainly not ne
Steven Flatt writes:
Can someone explain what is going on here? I can't quite figure it out
based on the docs.
Are you on FreeBSD by any chance?
I think the FreeBSD port by default installs a script that does a daily
vacuum. If using another OS, perhaps you want to see if you used some sor
Steven Flatt wrote:
The bad thing, which I don't totally understand from reading the docs, is
that another db-wide vacuum kicked off exactly 24 hours after the first
db-wide vacuum kicked off, before the first one had finished. (Note that
these vacuums seem to go through the tables alphabeticall
We recently upgraded a very large database (~550 GB) from 8.1.4 to 8.2.4 via
a pg_dump and pg_restore. (Note that the restore took several days.) We
had accepted the default settings:
vacuum_freeze_min_age = 100 million
autovacuum_freeze_max_age = 200 million
Due to our very high transaction r
11 matches
Mail list logo
