Re: PITR

2014-02-22 18:31 GMT+01:00 Julien Rouhaud <julien(dot)rouhaud(at)dalibo(dot)com>:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Le 22/02/2014 18:03, Murthy Nunna a écrit :
> > Mat,
> >
> >
> >
> > Thank you for your quick response....
> >
> >
> >
> > The documentation says for pause_at_recovery_target:
> >
> >
> >
> > This setting has no effect if hot_standby
> > <
> http://www.postgresql.org/docs/9.2/static/runtime-config-replication.html#GUC-HOT-STANDBY
> >
> > is not enabled, or if no recovery target is set.
> >
> >
> >
> > In my case hot_standby is not enabled.
> >
> >
> Hi,
>
> If you want to connect to your database in read only to check the
> recovery point, you have to enable it. It doesn't have any impact when
> the cluster is not in recovery mode.
>
> Regards.
>
> >
> > Thanks,
> >
> > Murthy
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > *From:*desmodemone [mailto:desmodemone(at)gmail(dot)com] *Sent:* Saturday,
> > February 22, 2014 10:34 AM *To:* Murthy Nunna *Cc:*
> > pgsql-admin(at)postgresql(dot)org *Subject:* Re: [ADMIN] PITR
> >
> >
> >
> >
> >
> >
> >
> > 2014-02-22 17:06 GMT+01:00 Murthy Nunna <mnunna(at)fnal(dot)gov
> > <mailto:mnunna(at)fnal(dot)gov>>:
> >
> > All,
> >
> >
> >
> > I am testing PITR.... I am looking for recovery.conf parameters where
> > you can recovery the WALs available in the restore_command but do
> > not complete recovery. I want to be able to connect to the database
> > and check database in read only and if I am not there yet, I will
> > feed more WALs in the archive directory and resume recovery. I
> > would like to prevent multiple base restorations. I want to roll
> > forward with WALs but check in between. Also, I do not want to set
> > up replication standby.
> >
> >
> >
> > Is it possible? If so, could you tell me what are the relevant
> > recovery.conf params?
> >
> >
> >
> > Thanks,
> >
> > Murthy
> >
> >
> >
> > Hi Murthy, look at parameter "pause_at_recovery_target" and
> > "recovery_target_time" with these parameters in the recovery.conf
> > you could reach a point in the timeline to recover the database and
> > then see if it's all ok and then finish the recovery with
> > pg_xlog_replay_resume. If you want instead continue the recovery
> > you have to stop the backend and change the parameter of
> > recovery_target_time in the recovery.conf and restart the
> > postmaster.
> >
> > Mat DBA
> >
> >
> >
>
>
> - --
> Julien Rouhaud
> http://dalibo.com - http://dalibo.org
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.11 (GNU/Linux)
> Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
>
> iQEcBAEBAgAGBQJTCN8GAAoJELGaJ8vfEpOqynAH/1Vu2gUwdDww26qbbDreXRid
> kpWGUEI2YXBw4e6D3SFiFDG77aPwFF7aGDXs/3Rjck3erLaYrtj/70ZFEwXJ2d4K
> W2hDS8KFt8cx6YsNMI2epL/FnDYZKudU2Qcceixlzf2gGSDeexyy/ZLdTOQMgXZF
> D4ktuEOdpIxUDipbWe7af2TVzaiTqHEu64RtcmtgPWIlwJHdtShEYFo6Go0BryY9
> ToU+8DU45x4tuH6msk94D/7/NQJnkMpPNztxAXXZsDp4Xwtrq3nA20187y69NVu8
> uWSpJVFzfPZIV0Cl6vupyw2k6G9ObvTBWcpSPrixVjgcpiHh+15j49z+OTfSB1I=
> =FR3m
> -----END PGP SIGNATURE-----
>
>
> --
> Sent via pgsql-admin mailing list (pgsql-admin(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-admin
>

+1 for Julien

Mat DBA