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
; 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
2012 at 3:30 PM, Bruce Momjian wrote:
> 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
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 successfull
edb1:/data/pg$ vacuumdb --all --analyze-only
53. vacuumdb: vacuuming database "functionx"
54. vacuumdb: vacuuming database "postgres"
55. vacuumdb: vacuuming of database "postgres" failed: ERROR: could not
access status of transaction 46675125
56. DETAIL: Could not open file "pg_clog/002C": No such file or
directory.
57. postgres@sparedb1:/data/pg$
Regards,
Payal Singh
