Re: "an SQL" vs. "a SQL" - Mailing list pgsql-hackers

From David Rowley
Subject Re: "an SQL" vs. "a SQL"
Date
Msg-id CAApHDvpy6MGhUEBoPYQGKzXzGxRzf6aKenndtfbCKG=7tsV1Lg@mail.gmail.com
Whole thread Raw
In response to Re: "an SQL" vs. "a SQL"  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: "an SQL" vs. "a SQL"
List pgsql-hackers
On Fri, 11 Jun 2021 at 02:53, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Indeed.  I think this is entirely pointless; there's zero hope that
> any consistency you might establish right now will persist very long.
> The largest effect of this proposed patch will be to create
> back-patching headaches.

hmm.  Yet we do have other standards which we do manage to maintain.

I did limit the scope to just the docs and error messages. My thoughts
were that someone fudging a backpatch on the docs seems less likely to
cause a nuclear meltdown than someone doing the same in .c code.

David



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: "an SQL" vs. "a SQL"
Next
From: Matthias van de Meent
Date:
Subject: Re: pg14b1 stuck in lazy_scan_prune/heap_page_prune of pg_statistic