Okay. I guess so. Thanks for your help.
Regards,
Payal
On Fri, Jul 6, 2012 at 4:24 PM, Bruce Momjian wrote:
> On Fri, Jul 06, 2012 at 04:21:06PM -0400, Payal Singh wrote:
> > If something was wrong with the cluster, why did vacuumdb on new server
> run
> > successfully when I followed Craig's s
On Fri, Jul 06, 2012 at 04:21:06PM -0400, Payal Singh wrote:
> If something was wrong with the cluster, why did vacuumdb on new server run
> successfully when I followed Craig's suggestion of running vacuumdb on old
> server first, before performing the upgrade, and then ran vacuumdb on new one?
M
If something was wrong with the cluster, why did vacuumdb on new server run
successfully when I followed Craig's suggestion of running vacuumdb on old
server first, before performing the upgrade, and then ran vacuumdb on new
one?
On Fri, Jul 6, 2012 at 4:05 PM, Bruce Momjian wrote:
> On Fri, Jul
On Fri, Jul 06, 2012 at 04:03:38PM -0400, Payal Singh wrote:
> The omnipitr-backup-slave process takes online backups from the standby, and
> this is done everyday. This process connects to the master and calls a
> pg_start_backup and then looks for a restore point on the standby after that
> WAL a
The omnipitr-backup-slave process takes online backups from the standby,
and this is done everyday. This process connects to the master and calls a
pg_start_backup and then looks for a restore point on the standby after
that WAL address. So i don't think I need to shut down the server.
Also, it is
On Fri, Jul 06, 2012 at 02:22:28PM -0400, Payal Singh wrote:
> The first message in the log is probably because the backup is taken from a
> standby. I am using omnipitr-backup-slave to make the backups and then
> restoring one of those.
OK, this is what I wanted to see. Is the server running whi
On Fri, Jul 06, 2012 at 01:20:21PM -0400, Payal Singh wrote:
> Hi,
>
> I restored the backup on 9.1, made sure the database reached a consistent
> state
> and checkpointed. Then I performed the upgrade. Upgrade completed successfully
> but on running vacuumdb it gave the exact same error. The con
On Thu, Jul 05, 2012 at 06:28:31PM -0400, Tom Lane wrote:
> Payal Singh writes:
> > On Thu, Jul 5, 2012 at 12:15 PM, Craig Ringer wrote:
> >> If you start 9.1 on a copy of the backup then cleanly stop it again, does
> >> pg_upgrade then run?
>
> > Thank you. That worked.
>
> ISTM that pg_upgrad
Payal Singh writes:
> On Thu, Jul 5, 2012 at 12:15 PM, Craig Ringer wrote:
>> If you start 9.1 on a copy of the backup then cleanly stop it again, does
>> pg_upgrade then run?
> Thank you. That worked.
ISTM that pg_upgrade should check that the old cluster was shut down
cleanly, ie pg_control h
Thank you. That worked.
Regards
Payal
On Thu, Jul 5, 2012 at 12:15 PM, Craig Ringer wrote:
> On 07/05/2012 11:20 PM, Payal Singh wrote:
>
> Hello,
>
> I am trying to use pg_upgrade to upgrade data from 9.1.4 to 9.2beta2.
> Although the upgrade completed successfully, vacuumdb --all --analyze
On 07/05/2012 11:20 PM, Payal Singh wrote:
Hello,
I am trying to use pg_upgrade to upgrade data from 9.1.4 to 9.2beta2.
Although the upgrade completed successfully, vacuumdb --all
--analyze-only gives an error. I tried upgrading two binary backups of
the same production database from differen
11 matches
Mail list logo
