Re: Error on failed COMMIT

From: Vik Fearing <vik(at)postgresfriends(dot)org>
To: Dave Cramer <davecramer(at)postgres(dot)rocks>, Bruce Momjian <bruce(at)momjian(dot)us>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, Vladimir Sitnikov <sitnikov(dot)vladimir(at)gmail(dot)com>, Shay Rojansky <roji(at)roji(dot)org>, "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-03-30 16:32:16
Message-ID: 42af8c1c-cca3-c518-dbc7-8fe828519719@postgresfriends.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 3/30/20 6:05 PM, Dave Cramer wrote:
> So it appears this is currently languishing as unresolved and feature
> freeze is imminent.
>
> What has to be done to get a decision one way or another before feature
> freeze.
>
> I have provided a patch that could be reviewed and at least be considered
> in the commitfest.
>
> Perhaps someone can review the patch and I can do whatever it takes to get
> it presentable ?

I don't know enough about that part of the code to give a meaningful
review, but I will give my full support to the patch. (I hadn't
expressed an opinion either way yet.)
--
Vik Fearing

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Fujii Masao 2020-03-30 16:36:18 Re: Planning counters in pg_stat_statements (using pgss_store)
Previous Message Justin Pryzby 2020-03-30 16:26:16 Re: error context for vacuum to include block number