Re: Improve documentation for pg_upgrade, standbys and rsync - Mailing list pgsql-docs

From Laurenz Albe
Subject Re: Improve documentation for pg_upgrade, standbys and rsync
Date
Msg-id ddb672a7631302921eda7dfc1b1629dc0c6de988.camel@cybertec.at
Whole thread Raw
In response to Improve documentation for pg_upgrade, standbys and rsync  (Laurenz Albe <laurenz.albe@cybertec.at>)
List pgsql-docs
On Tue, 2022-04-05 at 13:10 -0400, Stephen Frost wrote:
> * Robert Haas (robertmhaas@gmail.com) wrote:
> On Mon, Jul 26, 2021 at 3:11 PM Stephen Frost <sfrost@snowman.net> wrote:
> > * Laurenz Albe (laurenz.albe@cybertec.at) wrote:
> > > > Thanks for looking at this!
> > > 
> > > Sure.  Thanks for working on it!
> > 
> > Stephen, do you intend to do something about this patch in terms of
> > getting it committed? You're the only reviewer but haven't responded
> > to the thread for more than 5 months.
> 
> I tried to be clear in the last email on the thread, the one which you
> just responded to, here:
> 
> * Stephen Frost (sfrost@snowman.net) wrote:
> > This, of course, all comes back to the original complaint I had about
> > documenting this approach, which is that these things should only be
> > done by someone extremely familiar with the PG codebase, until and
> > unless we write an actual tool to do this.
> 
> To be more explicit though- we should write a tool to do this.  We
> shouldn't try to document a way to do it because it's hard to get right.

I see no agreement on this patch.  I'll withdraw it from the commitfest
to avoid hogging resources.  Thanks everyone for the review.

Yours,
Laurenz Albe




pgsql-docs by date:

Previous
From: Laurenz Albe
Date:
Subject: Re: Improve documentation for pg_upgrade, standbys and rsync
Next
From: PG Doc comments form
Date:
Subject: 41.3. Materialized Views: Create table should be create view?