Re: Error on failed COMMIT - Mailing list pgsql-hackers

From Masahiko Sawada
Subject Re: Error on failed COMMIT
Date
Msg-id CAD21AoCrfs+m86-7Y_ph2ifqvn8MegtGnzC3gA+3pN3jSwfD8A@mail.gmail.com
Whole thread Raw
In response to Re: Error on failed COMMIT  (Dave Cramer <davecramer@postgres.rocks>)
List pgsql-hackers
On Thu, Jan 7, 2021 at 11:29 PM Dave Cramer <davecramer@postgres.rocks> wrote:
>
> I could if someone wants to commit to reviewing it.
> I've updated it a number of times but it seems nobody wants to review it.

Since this has a long thread, how about summarizing what consensus we
reached and what discussion we still need if any so that new reviewers
can easily catch up? I think people who want to start reviewing are
likely to search the patch marked as "Needs Review". So I think
continuous updating and rebasing the patch would help get the patch
reviewed also in terms of that.

Regards,

-- 
Masahiko Sawada
EDB:  https://www.enterprisedb.com/



pgsql-hackers by date:

Previous
From: Pavel Stehule
Date:
Subject: Re: plpgsql variable assignment not supporting distinct anymore
Next
From: Masahiko Sawada
Date:
Subject: Re: LogwrtResult contended spinlock