Chris Travers wrote:
> John R Pierce 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 second copy (without the
bloat) while i
On Wed, Oct 9, 2013 at 7:04 PM, John R Pierce 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 are also hav
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 i
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
On Tue, Oct 8, 2013 at 8:25 AM, shailesh singh wrote:
> 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?
yes i am executing psql to connect to this database.
su - postgres
psql patnadbold
On Tue, Oct 8, 2013 at 8:48 PM, bricklen wrote:
>
>
>
> On Tue, Oct 8, 2013 at 8:13 AM, shailesh singh wrote:
>
>>
>> On Tue, Oct 8, 2013 at 8:36 PM, bricklen wrote:
>>
>>>
>>> On Tue, Oct 8, 2013 at 8
On Tue, Oct 8, 2013 at 8:13 AM, shailesh singh wrote:
>
> On Tue, Oct 8, 2013 at 8:36 PM, bricklen wrote:
>
>>
>> On Tue, Oct 8, 2013 at 8:03 AM, shailesh singh wrote:
>>
>>> HINT: To avoid a database shutdown, execute a full-database VACUUM in
>>> "patnadbold".
>>> ERROR: could not access status
On Tue, Oct 08, 2013 at 08:06:50AM -0700, bricklen wrote:
> On Tue, Oct 8, 2013 at 8:03 AM, shailesh singh 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 "p
On Tue, Oct 8, 2013 at 8:03 AM, shailesh singh 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/": No such file or directory
> exit
>
>
> After this i am a
