On Tuesday, May 23, 2023, Tom Lane wrote:
> Laurenz Albe writes:
> > On Wed, 2023-05-24 at 07:32 +0900, Michael Paquier wrote:
> >> This is the current sentence, and it sounds kind of OK to me, FWIW:
> >> "Postgres95 code was completely ANSI C and trimmed in size by 25%.
>
> > That uses "ANSI C"
Laurenz Albe writes:
> On Wed, 2023-05-24 at 07:32 +0900, Michael Paquier wrote:
>> This is the current sentence, and it sounds kind of OK to me, FWIW:
>> "Postgres95 code was completely ANSI C and trimmed in size by 25%.
> That uses "ANSI C" as an adjective, which I think is sloppy wording
> (ev
On Wed, 2023-05-24 at 07:32 +0900, Michael Paquier wrote:
> On Tue, May 23, 2023 at 08:52:25PM +, PG Doc comments form wrote:
> > There appears to be a typo, here:
> > https://www.postgresql.org/docs/current/history.html#:~:text=Postgres95%20code%20was%20completely%20ANSI%20C.
> > A word or two
On Tue, May 23, 2023 at 3:32 PM Michael Paquier wrote:
> On Tue, May 23, 2023 at 08:52:25PM +, PG Doc comments form wrote:
> > There appears to be a typo, here:
> >
> https://www.postgresql.org/docs/current/history.html#:~:text=Postgres95%20code%20was%20completely%20ANSI%20C
> .
> > A word or
On Tue, May 23, 2023 at 08:52:25PM +, PG Doc comments form wrote:
> There appears to be a typo, here:
> https://www.postgresql.org/docs/current/history.html#:~:text=Postgres95%20code%20was%20completely%20ANSI%20C.
> A word or two should be added between 'completely' and 'ANSI C', such as
> 're-
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/15/history.html
Description:
Hi Folks, thank you for maintaining this great technical resource, which
I've only recently started to use.
There appears to be a typo, here:
https://www.postgre
