Re: [BUGS] BUG #14898: pg_upgrade documentation is misleading - Mailing list pgsql-bugs

From Bruce Momjian
Subject Re: [BUGS] BUG #14898: pg_upgrade documentation is misleading
Date
Msg-id 20180123172830.GA31548@momjian.us
Whole thread Raw
In response to [BUGS] BUG #14898: pg_upgrade documentation is misleading  (yves.goergen@gmail.com)
Responses Re: [BUGS] BUG #14898: pg_upgrade documentation is misleading
List pgsql-bugs
On Fri, Nov 10, 2017 at 10:09:12PM +0000, yves.goergen@gmail.com wrote:
> The following bug has been logged on the website:
> 
> Bug reference:      14898
> Logged by:          Yves Goergen
> Email address:      yves.goergen@gmail.com
> PostgreSQL version: 10.0
> Operating system:   Ubuntu
> Description:        
> 
> The documentation of pg_upgrade suggests that -d and -D are the data
> directories. But actually they expect the config directories. In a default
> installation from the official packages for Ubuntu (from PostgreSQL, not
> from Ubuntu), this is a difference between /var/lib/postgresql/10/main and
> /etc/postgresql/10/main. See also https://dba.stackexchange.com/q/190469

I think you are correct.  We have tried to adjust our documentation to
show the most common implementation locations, but at the same time to
be accurate.  For example, in the the 'postgres' manual page, we kept -D
(signifying datadir) but describe it as the location of the
configuration files, e.g.

       -D datadir
           Specifies the file system location of the database
           configuration files.

This was not done with pg_upgrade, and the attached patch fixes that.  I
am thinking of applying this to PG 10 and head (PG 11)  but not
backpatching it further.

-- 
  Bruce Momjian  <bruce@momjian.us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

+ As you are, so once was I.  As I am, so you will be. +
+                      Ancient Roman grave inscription +

Attachment

pgsql-bugs by date:

Previous
From: Rainer Orth
Date:
Subject: Conflicting declarations for b64_encode etc. on Solaris 11.4 Beta
Next
From: Elvis Pranskevichus
Date:
Subject: ERROR: could not devise a query plan for the given query (UNIONS and LATERAL)