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 because it has some features that will help avoid some issues.
Try:
vacuumdb -a
Or if you want to force reclaim space (if you are suffering from db bloat relating to not vacuuming:
vacuumdb -f -a
You may need to run this as the postgres user. It accepts the same parameters for authentication that psql does.
Best Wishes,
Chris Travers
On Tue, Oct 8, 2013 at 8:25 AM, shailesh singh <shaileshjuly@xxxxxxxxx> wrote:
yes i am executing psql to connect to this database.su - postgres
psql patnadbold
On Tue, Oct 8, 2013 at 8:48 PM, bricklen <bricklen@xxxxxxxxx> wrote:
On Tue, Oct 8, 2013 at 8:13 AM, shailesh singh <shaileshjuly@xxxxxxxxx> wrote:
On Tue, Oct 8, 2013 at 8:36 PM, bricklen <bricklen@xxxxxxxxx> wrote:
On Tue, Oct 8, 2013 at 8:03 AM, shailesh singh <shaileshjuly@xxxxxxxxx> wrote:
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/0000": No such file or directoryexitAfter this i am able to stop /start my db server but i am not able to connect to my databases (it tells to run vacuum full first on patnadbold databases)The message does *not* say to run "VACUUM FULL", it says to run a "full-database VACUUM". Different things.
Connect to "patnadbold" and issue "VACUUM;" (without double-quotes) as the others have suggested.
Thanks.When i am trying to connect "patnadbold" , it is giving error for "execute a full-database VACUUM in "patnadbold" " .is there any way to connect this database using backend process . pl let me know the command sequnce i need to run.
Please keep replies CC'd to the pgsql-general list, and follow the format of the other messages, which is to bottom-post.You need to show (again?) exactly what you are executing. Are you connecting via psql or using another command? Are you connecting directly to that "patnadbold" database? If you are able to connect to it, are you able to issue just "VACUUM;" ?
Best Wishes,
Chris Travers
Efficito: Hosted Accounting and ERP. Robust and Flexible. No vendor lock-in.
