On Wed, Oct 9, 2013 at 7:04 PM, John R Pierce pie...@hogranch.com wrote:
On 10/8/2013 8:35 AM, Chris Travers wrote:
First, while vacuum is usually preferred to vacuum full, in this case, I
usually find that vacuum full clears up enough cruft to be worth it (not
always, but especially if you
Chris Travers chris.trav...@gmail.com wrote:
John R Pierce pie...@hogranch.com wrote:
I often find in those cases it is a choice between vacuum full
and dumpall/initdb/reload/analyze.
Way back in the 8.1 days I often found CLUSTER to be my best option
-- as long as I had room enough for a
On 10/8/2013 8:35 AM, Chris Travers wrote:
First, while vacuum is usually preferred to vacuum full, in this case,
I usually find that vacuum full clears up enough cruft to be worth it
(not always, but especially if you are also having performance issues).
IIRC, vacuum full was pretty broken
On Tue, Oct 8, 2013 at 8:03 AM, shailesh singh shaileshj...@gmail.comwrote:
HINT: To avoid a database shutdown, execute a full-database VACUUM in
patnadbold.
ERROR: could not access status of transaction 33011
DETAIL: could not open file pg_clog/: No such file or directory
exit
After
On Tue, Oct 08, 2013 at 08:06:50AM -0700, bricklen wrote:
On Tue, Oct 8, 2013 at 8:03 AM, shailesh singh shaileshj...@gmail.comwrote:
HINT: To avoid a database shutdown, execute a full-database VACUUM in
patnadbold.
ERROR: could not access status of transaction 33011
DETAIL: could not
On Tue, Oct 8, 2013 at 8:13 AM, shailesh singh shaileshj...@gmail.comwrote:
On Tue, Oct 8, 2013 at 8:36 PM, bricklen brick...@gmail.com wrote:
On Tue, Oct 8, 2013 at 8:03 AM, shailesh singh shaileshj...@gmail.comwrote:
HINT: To avoid a database shutdown, execute a full-database VACUUM in
yes i am executing psql to connect to this database.
su - postgres
psql patnadbold
On Tue, Oct 8, 2013 at 8:48 PM, bricklen brick...@gmail.com wrote:
On Tue, Oct 8, 2013 at 8:13 AM, shailesh singh shaileshj...@gmail.comwrote:
On Tue, Oct 8, 2013 at 8:36 PM, bricklen
On Tue, Oct 8, 2013 at 8:25 AM, shailesh singh shaileshj...@gmail.comwrote:
yes i am executing psql to connect to this database.
su - postgres
psql patnadbold
..and then what? Does it immediately throw an error stating that you must
issue a VACUUM?
First, while vacuum is usually preferred to vacuum full, in this case, I
usually find that vacuum full clears up enough cruft to be worth it (not
always, but especially if you are also having performance issues).
Secondly I would recommend using the vacuumdb command from the shell
instead of psql
