| From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
|---|---|
| To: | "Dean Gibson (DB Administrator)" <postgresql(at)mailpen(dot)com>, pgsql-general <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Cc: | Scott Honaker <scott(dot)n7ss(at)gmail(dot)com>, Grant Hopper <kb7wsd(at)gmail(dot)com>, Erik Robins <erik(dot)robins(at)gmail(dot)com> |
| Subject: | Re: bottom / top posting |
| Date: | 2021-06-09 23:50:58 |
| Message-ID: | 49f1e9f5-ba8f-9eed-f931-500ad7ca3f3f@aklaver.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 6/9/21 2:41 PM, Dean Gibson (DB Administrator) wrote:
>
>> On Mon, Jun 7, 2021 at 07:53:30PM +0200, Francisco Olarte wrote:
>>> ... properly scanning a top posted one takes much longer.
>
> I wonder about the tolerance of the world we live in. Somehow, I can
> deal with top-posting, bottom-posting, middle-posting, HTML eMail,
> straight-text eMails, 80-column eMails, variable-width eMails,
> occasional ALL CAPS eMails, & stupid multi-line signatures, all without
> getting my tail in a knot over it.
>
Think of it as a conforming to a style guide when writing for a
publication. In this case the style is preferred for the reasons Tom
Lane stated in his post.
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Lucas | 2021-06-10 01:16:18 | PostgreSQL replication lag - Suggestions and questions |
| Previous Message | Dave Cramer | 2021-06-09 22:43:16 | Re: bottom / top posting |