On Wed, Sep 27, 2023 at 09:42:49AM +0200, Daniel Gustafsson wrote:
> > On 26 Sep 2023, at 22:26, Bruce Momjian wrote:
> > On Tue, Sep 26, 2023 at 10:56:27AM -0700, David G. Johnston wrote:
>
> >> I would get rid of any mentions of our old pre-v10 versioning scheme in the
> >> current
> On 26 Sep 2023, at 22:26, Bruce Momjian wrote:
> On Tue, Sep 26, 2023 at 10:56:27AM -0700, David G. Johnston wrote:
>> I would get rid of any mentions of our old pre-v10 versioning scheme in the
>> current documentation.
For content such as this, a very big +1.
> Good point, how is this
On Tue, Sep 26, 2023 at 10:56:27AM -0700, David G. Johnston wrote:
> On Tue, Sep 26, 2023 at 10:35 AM Bruce Momjian wrote:
>
> On Mon, Sep 18, 2023 at 08:14:04PM +, PG Doc comments form wrote:
> > The following documentation comment has been logged on the website:
> >
> >
On Tue, Sep 26, 2023 at 10:35 AM Bruce Momjian wrote:
> On Mon, Sep 18, 2023 at 08:14:04PM +, PG Doc comments form wrote:
> > The following documentation comment has been logged on the website:
> >
> > Page: https://www.postgresql.org/docs/16/pgupgrade.html
> > Description:
> >
> > I feel
On Mon, Sep 18, 2023 at 08:14:04PM +, PG Doc comments form wrote:
> The following documentation comment has been logged on the website:
>
> Page: https://www.postgresql.org/docs/16/pgupgrade.html
> Description:
>
> I feel like for readability the pg_upgrade doc should use the same
>
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/16/pgupgrade.html
Description:
I feel like for readability the pg_upgrade doc should use the same
old_version and new_version examples when showing examples throughout the
doc page.
as an
