Hi, On 2017-03-28 00:19:29 +0300, Stas Kelvich wrote: > Ok, here it is.
On a very quick skim, this doesn't seem to solve the issues around deadlocks of prepared transactions vs. catalog tables. What if the prepared transaction contains something like LOCK pg_class; (there's a lot more realistic examples)? Then decoding won't be able to continue, until that transaction is committed / aborted? - Andres -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
