Re: [GENERAL] pg_upgrade -u - Mailing list pgsql-hackers

From Ray Stell
Subject Re: [GENERAL] pg_upgrade -u
Date
Msg-id 39CAC308-CE20-410B-A4F5-810438C04E0A@vt.edu
Whole thread Raw
In response to Re: [GENERAL] pg_upgrade -u  (Bruce Momjian <bruce@momjian.us>)
Responses Re: [GENERAL] pg_upgrade -u  (Bruce Momjian <bruce@momjian.us>)
List pgsql-hackers
On May 29, 2013, at 11:07 AM, Bruce Momjian wrote:

> On Wed, May 29, 2013 at 08:59:42AM -0400, Ray Stell wrote:
>>> [ moved to hacker ]
>>> The question is whether hard-wiring these helps more than it hurts, and which ones should be hard-wired.

I seems to me that superuser is exactly that special case and that if an alternate superuser is hardwired in the src
clusterthen -u/-U and that specific value will be required on both sides of pg_upgrade, no variability is needed and
perhapsnot possible.  You're point is well taken for port. 


pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: removing PD_ALL_VISIBLE
Next
From: Stephen Frost
Date:
Subject: Re: fallocate / posix_fallocate for new WAL file creation (etc...)