Skip site navigation (1) Skip section navigation (2)

Re: Vacuumdb error

From: Carl von Clausewitz <clausewitz45(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Vacuumdb error
Date: 2011-04-14 20:17:54
Message-ID: BANLkTi=1XnC5fHK078X1Wj5+-hcHkmC0xA@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-general
Everything was fine, the reordered script fixed everything. Thanks all.

Regards,
Carl

2011/4/14 Carl von Clausewitz <clausewitz45(at)gmail(dot)com>

> Ok thanks, the information. I've made the mistake, I will change the
> script, but I will try, that Vidhya told me. Let me see, what will going
> on.
>
> Regards,
> Carl
>
> 2011/4/14 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
>
>> Carl von Clausewitz <clausewitz45(at)gmail(dot)com> writes:
>> > Maintenance:
>> > #!/bin/sh
>> > date >> /var/log/postgresql_maintenance.log
>> > /usr/local/bin/reindexdb --all --username=cvc >>
>> > /var/log/postgresql_maintenance.log
>> > echo "Reindex done" >> /var/log/postgresql_maintenance.log
>> > /usr/local/bin/vacuumdb --all --full --analyze --username=cvc >>
>> > /var/log/postgresql_maintenance.log
>> > echo "Vacuum done" >> /var/log/postgresql_maintenance.log
>>
>> Just FYI, the reindex step is 100% useless if you're going to do a
>> vacuum full afterwards.
>>
>> Before 9.0 there was some value in doing vacuum full and then reindex,
>> but none whatsoever in the other ordering.  As of 9.0 there's just no
>> point at all in doing both.  VACUUM FULL rebuilds the indexes anyway.
>>
>>                        regards, tom lane
>>
>
>

In response to

pgsql-general by date

Next:From: Scott MarloweDate: 2011-04-14 20:42:24
Subject: Re: SSDs with Postgresql?
Previous:From: David KerrDate: 2011-04-14 19:36:57
Subject: Re: Calculating memory allocaiton per process

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group