| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Petr Jelinek <petr(dot)jelinek(at)2ndquadrant(dot)com>, Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Re: [COMMITTERS] pgsql: Don't force-assign transaction id when exporting a snapshot. |
| Date: | 2017-08-14 17:55:29 |
| Message-ID: | 21237ba0-2c55-07f8-0e0c-846655f2c565@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
On 8/12/17 07:32, Petr Jelinek wrote:
> This commit has side effect that it makes it possible to export
> snapshots on the standbys. This makes it possible to do pg_dump -j on
> standby with consistent snapshot. Here is one line patch (+ doc update)
> which allows doing that when pg_dumping from PG10+.
>
> I also wonder if it should be mentioned in release notes. If the
> attached patch would make it into PG10 it would be no brainer to mention
> it as feature under pg_dump section, but exporting snapshots alone I am
> not sure about.
Any other opinions on this patch?
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2017-08-14 17:57:40 | Re: Re: [COMMITTERS] pgsql: Don't force-assign transaction id when exporting a snapshot. |
| Previous Message | Peter Eisentraut | 2017-08-14 17:53:27 | pgsql: Fix typo |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2017-08-14 17:57:40 | Re: Re: [COMMITTERS] pgsql: Don't force-assign transaction id when exporting a snapshot. |
| Previous Message | Peter Eisentraut | 2017-08-14 17:53:46 | Re: Fix a typo in sequence.c |