Re: clean up docs for v12

From: Justin Pryzby <pryzby(at)telsasoft(dot)com>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: clean up docs for v12
Date: 2019-04-26 17:17:22
Message-ID: 20190426171722.GB3925@telsasoft.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

On Tue, Apr 23, 2019 at 11:50:42AM +0900, Michael Paquier wrote:
> On Mon, Apr 22, 2019 at 12:19:55PM -0400, Alvaro Herrera wrote:
> > On 2019-Apr-22, Andres Freund wrote:
> >> I think it'd be better just to fix s/the all/that all/.
> >
> > (and s/if's/if it's/)
>
> FWIW, I have noticed that part when gathering all the pieces for what
> became 148266f, still the full paragraph was sort of confusing, so I
> have just fixed the most obvious issues reported first.

I saw you closed the item here:
https://wiki.postgresql.org/index.php?title=PostgreSQL_12_Open_Items&diff=33390&oldid=33389

But I think the biggest part of the patch is still not even reviewed ?
I'm referring to ./*review-docs-for-pg12dev.patch

I haven't updated the JIT changes since there's larger discussion regarding the
code.

Justin

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2019-04-26 18:57:49 Re: BUG #15672: PostgreSQL 11.1/11.2 crashed after dropping a partition table
Previous Message Tom Lane 2019-04-26 17:10:00 Re: BUG #15781: subselect on foreign table (postgres_fdw) can crash (segfault)