| From: | Andres Freund <andres(at)2ndquadrant(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Craig Ringer <craig(at)2ndquadrant(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Reporting the commit LSN at commit time |
| Date: | 2014-08-15 08:54:50 |
| Message-ID: | 20140815085450.GD28805@awork2.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2014-08-14 12:21:38 -0400, Robert Haas wrote:
> On Sat, Aug 9, 2014 at 12:54 PM, Andres Freund <andres(at)2ndquadrant(dot)com> wrote:
> > I don't think we really need to embed it at that level. And it doesn't
> > have to be always on - only clients that ask for it need to get the
> > answer. Something like COMMIT WITH (report_commit_lsn ON); or similar
> > might do the trick?
>
> And what does that actually do? Send back a result-set, or a new
> protocol message?
What I was thinking of was to return "COMMIT X/X" instead of
"COMMIT". Since that's only sent when COMMIT WITH (report_commit_lsn ON)
was set it won't break clients/libraries that don't need it.
Greetings,
Andres Freund
--
Andres Freund http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Marko Tiikkaja | 2014-08-15 08:55:04 | Re: pgcrypto: PGP armor headers |
| Previous Message | Andres Freund | 2014-08-15 08:25:35 | Re: pg_shmem_allocations view |