| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Christoph Berg <myon(at)debian(dot)org>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Craig Ringer <craig(at)2ndquadrant(dot)com>, PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: LSN as a recovery target |
| Date: | 2016-05-24 16:29:21 |
| Message-ID: | 20160524162921.GA430324@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Christoph Berg wrote:
> Re: Michael Paquier 2016-05-24 <CAB7nPqQRXsC8=ozh6GpjLnpZ=MeooUZOaAbzx28n2bjSMv2B4g(at)mail(dot)gmail(dot)com>
> > Yeah, that's really something that covers only a narrow case, though
> > if we don't have it when we need it we're limited to some hacks.
> > Perhaps people who have the advanced level to use such a thing have
> > the level to use hacks anyway..
>
> I'd think recovery_target_lsn would be more useful in practice than
> the existing recovery_target_xid. So I don't see why it shouldn't just
> be added, also given it's likely very unobtrusive to do so.
Also, see
http://www.postgresql.org/message-id/56BD0E4E.5050503@2ndquadrant.com
--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2016-05-24 16:32:12 | Re: LSN as a recovery target |
| Previous Message | Kevin Grittner | 2016-05-24 16:24:44 | Re: Re: [COMMITTERS] pgsql: Avoid extra locks in GetSnapshotData if old_snapshot_threshold < |