Re: pg_stat_statements: Remove (errcode...) framing parentheses in erport(...)

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Sami Imseih <samimseih(at)gmail(dot)com>
Cc: m(dot)litsarev(at)postgrespro(dot)ru, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: pg_stat_statements: Remove (errcode...) framing parentheses in erport(...)
Date: 2026-06-25 20:13:31
Message-ID: 1096184.1782418411@sss.pgh.pa.us
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Sami Imseih <samimseih(at)gmail(dot)com> writes:
> e3a87b499 states "There's no intention to make wholesale
> changes of existing ereport calls ..."

> Why do it for pg_stat_statements only when there are a bunch
> of other places?

I think we should flat out reject this patch. It makes no functional
improvement while creating a merge hazard for future back-patches.
That hazard might not be very large for just changing these few
spots, but any more-aggressive attempt at changing existing ereports'
style will certainly result in pain.

As e3a87b499 said, there was no plan to change existing code and
I think that decision should still stand.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bharath Rupireddy 2026-06-25 20:44:28 Re: Make pg_prewarm, autoprewarm yield for waiting DDL
Previous Message Alexander Nestorov 2026-06-25 20:07:00 Re: [PATCH] btree_gist: add cross-type integer operator support for GiST