| 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: | 2021-06-11 01:44:40 |
| Message-ID: | CAApHDvrW7gz_wASagySKd9iuzxiwndQvhhZE5Zj+gx4XNDj6qg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, 11 Jun 2021 at 04:04, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> However, I'm also
> unlikely to worry about this point when copy-editing docs.
I'm sorry to hear that. Maybe keeping this consistent will be one of
those endless jobs like keeping the source code pgindented. We still
try to keep that in order despite the audience for the source code
being much smaller than the audience for our documents.
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.
In the meantime, I've pushed the fixes to master.
David
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2021-06-11 01:49:50 | Re: pg14b1 stuck in lazy_scan_prune/heap_page_prune of pg_statistic |
| Previous Message | Noah Misch | 2021-06-11 01:43:44 | Re: Adjust pg_regress output for new long test names |