Re: Error on failed COMMIT

From: Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>
To: Dave Cramer <davecramer(at)postgres(dot)rocks>
Cc: Georgios Kokolatos <gkokolatos(at)protonmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Error on failed COMMIT
Date: 2021-01-22 14:27:35
Message-ID: CAD21AoCrfs+m86-7Y_ph2ifqvn8MegtGnzC3gA+3pN3jSwfD8A@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Jan 7, 2021 at 11:29 PM Dave Cramer <davecramer(at)postgres(dot)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/

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Masahiko Sawada 2021-01-22 14:28:46 Re: LogwrtResult contended spinlock
Previous Message Pavel Stehule 2021-01-22 14:27:00 Re: plpgsql variable assignment not supporting distinct anymore