Re: [HACKERS] Logical replication in the same cluster - Mailing list pgsql-hackers

From Tom Lane
Subject Re: [HACKERS] Logical replication in the same cluster
Date
Msg-id 19152.1493244140@sss.pgh.pa.us
Whole thread Raw
In response to Re: [HACKERS] Logical replication in the same cluster  (Petr Jelinek <petr.jelinek@2ndquadrant.com>)
Responses Re: [HACKERS] Logical replication in the same cluster  (Michael Paquier <michael.paquier@gmail.com>)
Re: [HACKERS] Logical replication in the same cluster  (Robert Haas <robertmhaas@gmail.com>)
Re: [HACKERS] Logical replication in the same cluster  (Albe Laurenz <laurenz.albe@wien.gv.at>)
List pgsql-hackers
Petr Jelinek <petr.jelinek@2ndquadrant.com> writes:
> On 26/04/17 18:59, Bruce Momjian wrote:
>> ... it just hangs.  My server logs say:

> Yes that's result of how logical replication slots work, the transaction
> that needs to finish is your transaction. It can be worked around by
> creating the slot manually via the SQL interface for example and create
> the subscription using WITH (NOCREATE SLOT, SLOT NAME = 'your slot') .

If that's a predictable deadlock, I think a minimum expectation is that
the system should notice it and throw an error, not just hang.  (Then
the error could give a hint about how to work around it.)  But the case
Bruce has in mind doesn't seem like a crazy use-case to me.  Can't we
make it "just work"?
        regards, tom lane



pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: [HACKERS] Logical replication in the same cluster
Next
From: Thomas Munro
Date:
Subject: Re: [HACKERS] WIP: [[Parallel] Shared] Hash