On Monday 20 August 2007 14:33, Juliann Meyer wrote:
> Currently running v7.4.8 postgres on a RHE Linux 4.0 box. Will be
> upgraded to postgres 8.2.x sometime this fall.
>
> Several of the tables in the database that resides on this system have
> lots of inserts and updates. Very little is delet
Currently running v7.4.8 postgres on a RHE Linux 4.0 box. Will be
upgraded to postgres 8.2.x sometime this fall.
Several of the tables in the database that resides on this system have
lots of inserts and updates. Very little is deleted at this time, as
the database is intended for archiving
On Wed, 2005-03-16 at 11:55, Chris Hoover wrote:
> Tom,
>
> Thanks so much for the possible reason the vacuum fulls are not running.
>
> But, how about the first question. When you run a vacuum , who
> has access to the freed tuples? (only the table, the db, or the entire
> cluster)???
the t
Tom,
Thanks so much for the possible reason the vacuum fulls are not running.
But, how about the first question. When you run a vacuum , who
has access to the freed tuples? (only the table, the db, or the entire
cluster)???
Thanks,
Chris
---(end of broadcast)---
"Chris Hoover" <[EMAIL PROTECTED]> writes:
> We have also had one test occurrence where after the upgrade, a vacuum
> full would not recover the space. However, when we bounced the
> postmaster, and then performed a vacuum full, the space was recovered.
> Any ideas on what might cause this?
M
Question on vacuuming.
When you do a vacuum , are the "freed" tuples available only the
table, or to the entire db, or to the entire cluster?
The reason I'm asking is that we are getting ready to preform a major
upgrade to our application that involves adding some new fields to
almost every tab
