Re: Change "two" to "three" for decades of development in history - Mailing list pgsql-docs

From Pantelis Theodosiou
Subject Re: Change "two" to "three" for decades of development in history
Date
Msg-id CAE3TBxwPs9dYJ8+uUoraacBgLhVAmvAvG==ohs_BCv2o3Foa9w@mail.gmail.com
Whole thread Raw
In response to Re: Change "two" to "three" for decades of development in history  (Bruce Momjian <bruce@momjian.us>)
List pgsql-docs


On Sat, Jun 24, 2023 at 3:50 AM Bruce Momjian <bruce@momjian.us> wrote:
On Thu, Jun 22, 2023 at 10:01:45PM -0400, Jonathan Katz wrote:
> On 6/22/23 9:23 PM, Tom Lane wrote:
> > Michael Paquier <michael@paquier.xyz> writes:
> > > "With multiple decades of development behind it, PostgreSQL.."
> >
> > +1.  It sure seems silly trying to automate changing this.
>
> +1. With the proposed language, we can revisit it once it gets to
> "centuries."

Applied patch is "With decades of development".

+10 :) 

pgsql-docs by date:

Previous
From: Michael Paquier
Date:
Subject: Re: Change "two" to "three" for decades of development in history
Next
From: Dan Stoner
Date:
Subject: Re: streaming replication depends on matching glibc versions / LOCALE sort order