On Mon, Jan 20, 2020 at 11:10:25AM +, PG Doc comments form wrote:
> The following documentation comment has been logged on the website:
>
> Page: https://www.postgresql.org/docs/11/performance-tips.html
> Description:
>
> Hi, here:
> https://www.postgresql.org/download/products/6-postgresql-e
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/11/performance-tips.html
Description:
Hi, here:
https://www.postgresql.org/download/products/6-postgresql-extensions/
In section about: pg_track_settings
look for: that me must called
I'm not
On Mon, Jan 20, 2020 at 06:45:16PM +, Simon Riggs wrote:
> On Mon, 20 Jan 2020 at 16:03, Bruce Momjian wrote:
> Usually when I apply "wording" doc patches to head only, someone
> complains that it should be backpatched, so I did that in this case. If
> we want to change that idea,
On Mon, 20 Jan 2020 at 16:03, Bruce Momjian wrote:
> On Mon, Jan 20, 2020 at 12:23:48PM +0900, Ian Barwick wrote:
> > > I would hope to find correct documentation somewhere--that somewhere
> > > should be Postgresql's own documentation.
> >
> > Indeed, however it's important that the PostgreSQL d
On Mon, Jan 20, 2020 at 12:23:48PM +0900, Ian Barwick wrote:
> > I would hope to find correct documentation somewhere--that somewhere
> > should be Postgresql's own documentation.
>
> Indeed, however it's important that the PostgreSQL documentation remains
> stable for released versions.
>
> As-i
