Re: Change "two" to "three" for decades of development in history

2023-06-24 Thread Pantelis Theodosiou
On Sat, Jun 24, 2023 at 3:50 AM Bruce Momjian 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 writes: > > > > "With multiple decades of development behind it, PostgreSQL.." > > > > > > +1. It sure seems silly

Re: Change "two" to "three" for decades of development in history

2023-06-24 Thread Michael Paquier
On Fri, Jun 23, 2023 at 10:50:20PM -0400, Bruce Momjian wrote: > Applied patch is "With decades of development". Thanks. -- Michael signature.asc Description: PGP signature

Re: Change "two" to "three" for decades of development in history

2023-06-23 Thread Bruce Momjian
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 writes: > > > "With multiple decades of development behind it, PostgreSQL.." > > > > +1. It sure seems silly trying to automate changing this. > > +1. With the proposed

Re: Change "two" to "three" for decades of development in history

2023-06-22 Thread Jonathan S. Katz
On 6/22/23 9:23 PM, Tom Lane wrote: Michael Paquier 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." Jonathan

Re: Change "two" to "three" for decades of development in history

2023-06-22 Thread Tom Lane
Michael Paquier writes: > "With multiple decades of development behind it, PostgreSQL.." +1. It sure seems silly trying to automate changing this. regards, tom lane

Re: Change "two" to "three" for decades of development in history

2023-06-22 Thread Michael Paquier
On Fri, Jun 23, 2023 at 03:17:26AM +0200, Erik Wienhold wrote: > An SGML entity [0] or an xsltproc stringparam [1] looks viable. Question is > how to calculate the number of decades in the Makefile. It's trivial in SQL > :) - University of California at Berkeley. With over two decades of +

Re: Change "two" to "three" for decades of development in history

2023-06-22 Thread Erik Wienhold
> On 22/06/2023 23:00 CEST Bruce Momjian wrote: > > On Thu, Jun 22, 2023 at 01:47:16PM -0700, Kirk Parker wrote: > > > > I don't suppose DocBook has macro and system-variable capabilities? That > > could provide a set-and-forget solution to this? > > Uh, I am not aware of any. An SGML entity [0]

Re: Change "two" to "three" for decades of development in history

2023-06-22 Thread Bruce Momjian
On Thu, Jun 22, 2023 at 01:47:16PM -0700, Kirk Parker wrote: > > The following documentation comment has been logged on the website: > > > > Page: https://www.postgresql.org/docs/15/history.html > > Description: > > > > Hi, > > > > In

Re: Change "two" to "three" for decades of development in history

2023-06-22 Thread Kirk Parker
> > The following documentation comment has been logged on the website: > > > > Page: https://www.postgresql.org/docs/15/history.html > > Description: > > > > Hi, > > > > In https://www.postgresql.org/docs/current/history.html it is written > "With > > over two decades of development behind it". >

Re: Change "two" to "three" for decades of development in history

2023-06-21 Thread Bruce Momjian
On Tue, Jun 20, 2023 at 07:36:46AM +, PG Doc comments form wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/15/history.html > Description: > > Hi, > > In https://www.postgresql.org/docs/current/history.html it is written

Change "two" to "three" for decades of development in history

2023-06-20 Thread PG Doc comments form
The following documentation comment has been logged on the website: Page: https://www.postgresql.org/docs/15/history.html Description: Hi, In https://www.postgresql.org/docs/current/history.html it is written "With over two decades of development behind it". But since "The implementation of