| From: | David Rowley <dgrowleyml(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: "an SQL" vs. "a SQL" |
| Date: | 2024-04-09 04:18:00 |
| Message-ID: | CAApHDvp3osQwQam+wNTp9BdhP+QfWO6aY6ZTixQQMfM-UArKCw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, 11 Apr 2023 at 17:43, David Rowley <dgrowleyml(at)gmail(dot)com> wrote:
>
> On Fri, 11 Jun 2021 at 13:44, David Rowley <dgrowleyml(at)gmail(dot)com> wrote:
> > Anyway, I'll set an alarm for this time next year so I can check on
> > how many inconsistencies have crept back in over the development
> > cycle.
>
> That alarm went off today.
>
> There seem to be only 3 "a SQL"s in the docs to change to "an SQL".
>
> This is a pretty old thread, so here's a link [1] to the discussion.
>
> [1] https://postgr.es/m/CAApHDvpML27UqFXnrYO1MJddsKVMQoiZisPvsAGhKE_tsKXquw@mail.gmail.com
Link to the old thread above.
There's just 1 instance of "a SQL" that crept into PG16 after
d866f0374. This probably means I'd be better off doing this in June a
few weeks before branching...
Patch attached.
David
| Attachment | Content-Type | Size |
|---|---|---|
| use_an_SQL_not_a_SQL.patch | text/plain | 596 bytes |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Munro | 2024-04-09 04:18:28 | Streaming relation data out of order |
| Previous Message | Pavel Stehule | 2024-04-09 04:09:40 | Re: CASE control block broken by a single line comment |