Re: ERROR: subtransaction logged without previous top-level txn record

Arseny,

I was hoping you could give me some insights about how this bug might
appear with multiple replications slots. For example if I have two
replication slots would you expect both slots to see the same error, even
if they were started, consumed or the LSN was confirmed-flushed at
different times?

Dan

On Tue, Dec 17, 2019 at 10:15 AM Arseny Sher <a(dot)sher(at)postgrespro(dot)ru> wrote:

>
> Dan Katz <dkatz(at)joor(dot)com> writes:
>
> > Is the resolution of the issue in this thread being tracked elsewhere,
> > either in a commit fest or other stream of work?
>
> Ok, I've created a cf entry:
> https://commitfest.postgresql.org/26/2383/
>
> I believe it is the most important to commit at least
>
> 0002-Stop-demanding-that-top-xact-must-be-seen-before-sub.patch
>
> from my mail above -- as we see, this issue creates problems in the
> field. Moreover, the patch is trivial and hopefully I've shown that
> ERROR triggers were spurious and there is no easy way to relax the
> check.
>
> --
> Arseny Sher
> Postgres Professional: http://www.postgrespro.com
> The Russian Postgres Company
>