Re: Error on failed COMMIT

From: David Fetter <david(at)fetter(dot)org>
To: Vik Fearing <vik(at)postgresfriends(dot)org>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Shay Rojansky <roji(at)roji(dot)org>, Dave Cramer <davecramer(at)postgres(dot)rocks>, "Haumacher, Bernhard" <haui(at)haumacher(dot)de>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Error on failed COMMIT
Date: 2020-02-24 17:53:34
Message-ID: 20200224175334.GE13804@fetter.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Feb 24, 2020 at 06:40:16PM +0100, Vik Fearing wrote:
> On 24/02/2020 18:37, David Fetter wrote:
>
> > If we'd done this from a clean sheet of paper, it would have been the
> > right decision. We're not there, and haven't been for decades.
>
> OTOH, it's never too late to do the right thing.

Some right things take a lot of prep work in order to actually be
right things. This is one of them. Defaulting to SERIALIZABLE
isolation is another.

Best,
David.
--
David Fetter <david(at)fetter(dot)org> http://fetter.org/
Phone: +1 415 235 3778

Remember to vote!
Consider donating to Postgres: http://www.postgresql.org/about/donate

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Juan José Santamaría Flecha 2020-02-24 17:56:05 Re: BUG #16108: Colorization to the output of command-line has unproperly behaviors at Windows platform
Previous Message Tom Lane 2020-02-24 17:49:03 Re: Unicode escapes with any backend encoding