From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Andres Freund <andres(at)anarazel(dot)de> |
Cc: | Petr Jelinek <petr(dot)jelinek(at)2ndquadrant(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
Subject: | Re: logical replication busy-waiting on a lock |
Date: | 2017-06-02 01:38:41 |
Message-ID: | CA+TgmobJL4=Q0e92HSNeGTHBNvEdus1YuFZ2KKi9fAUh+f=dfg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, Jun 1, 2017 at 2:28 PM, Andres Freund <andres(at)anarazel(dot)de> wrote:
> On 2017-06-01 14:17:44 +0200, Petr Jelinek wrote:
>> Thinking more about this, I am not convinced it's a good idea to change
>> exports this late in the cycle. I still think it's best to do the xid
>> assignment only when the snapshot is actually exported but don't assign
>> xid when the export is only used by the local session (the new option in
>> PG10). That's one line change which impacts only logical
>> replication/decoding as opposed to everything else which uses exported
>> snapshots.
>
> I'm not quite convinced by this argument. Exported snapshot contents
> are ephemeral, we can change the format at any time. The wait is fairly
> annoying for every user of logical decoding. For me the combination of
> those two fact implies that we should rather fix this properly.
+1. The change Andres is proposing doesn't sound like it will be
terribly high-impact, and I think we'll be happier in the long run if
we install real fixes instead of kludging it.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2017-06-02 01:42:41 | Re: Error while creating subscription when server is running in single user mode |
Previous Message | Robert Haas | 2017-06-02 01:36:25 | Re: BEFORE trigger can cause undetected partition constraint violation |