On 9/22/2010 12:18 PM, Scott Marlowe wrote:
On Tue, Sep 21, 2010 at 9:10 PM, Christopher Gorge A. Marges
wrote:
But how would the newer version prevent bloat and eliminate making the
database unavailable while the *maintenance* goes on?
The database is more than five years old, and we did n
On Tue, Sep 21, 2010 at 9:10 PM, Christopher Gorge A. Marges
wrote:
> But how would the newer version prevent bloat and eliminate making the
> database unavailable while the *maintenance* goes on?
>
> The database is more than five years old, and we did not delete records
> until recently and when
But how would the newer version prevent bloat and eliminate making the
database unavailable while the *maintenance* goes on?
The database is more than five years old, and we did not delete records
until recently and when we do delete them, naturally the records are in
front of the table and t
On Tue, 2010-09-21 at 20:39 +0800, Christopher Gorge A. Marges wrote:
> We are using 7.4.13 and run the pg_autovacuum. Over the years, the
> database has grown so our maintenance plan was to "move" everything
> except for the last year. Since the server is kept up always using a
> full vacuum is
try reindex database;
and move away from 7.4, it is unsupported, and ancient history.
--
GJ
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general