Did not know that page even exists.
No need to enumerate. It would be nice if you mention that `This tool is
not suitable for restoring data in different major version`.
On Mon, Sep 18, 2023 at 4:08 PM Laurenz Albe
wrote:
> On Mon, 2023-09-18 at 15:29 +, PG Doc comments form wrote:
> > The
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
On Mon, Sep 18, 2023 at 10:08:30PM +0200, Laurenz Albe wrote:
> On Mon, 2023-09-18 at 15:29 +, PG Doc comments form wrote:
>> My main issue is that `pg_basebackup` page does not mention that this backup
>> is compatible only with current version of database. I can not do basebackup
>> on v11 an
On Mon, 2023-09-18 at 15:29 +, PG Doc comments form wrote:
> The following documentation comment has been logged on the website:
>
> Page: https://www.postgresql.org/docs/16/app-pgbasebackup.html
> Description:
>
> https://www.postgresql.org/docs/current/logical-replication.html
> Logical rep
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/16/app-pgbasebackup.html
Description:
https://www.postgresql.org/docs/current/logical-replication.html
Logical replication has excellent paragraph about usecases.
These pages does not have t
> On 13 Sep 2023, at 22:10, Boshomi Phenix wrote:
>
> Am Di., 12. Sept. 2023 um 12:25 Uhr schrieb Daniel Gustafsson
> mailto:dan...@yesql.se>>:
>
> Considering that we don't really have the OPTIONS syntax documented in an
> example, and that we reference COPY heavily on this page, I tend to agr
