| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Ray Stell <stellr(at)vt(dot)edu> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgreSQL(dot)org> |
| Subject: | Re: [GENERAL] pg_upgrade -u |
| Date: | 2013-06-28 23:14:28 |
| Message-ID: | 20130628231428.GC13790@momjian.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
On Thu, May 30, 2013 at 08:42:21AM -0400, Ray Stell wrote:
>
> 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 cluster then -u/-U and
> that specific value will be required on both sides of pg_upgrade, no
> variability is needed and perhaps not possible. You're point is well
> taken for port.
You have convinced me. The attached, applied patch for PG 9.4 passes
the command-line-supplied username into the created analyze script.
I have also attached a sample output analyze script.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
| Attachment | Content-Type | Size |
|---|---|---|
| username.diff | text/x-diff | 5.1 KB |
| analyze_new_cluster.sh | application/x-sh | 1.5 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2013-06-29 01:15:31 | Re: [GENERAL] pg_upgrade -u |
| Previous Message | Bruce Momjian | 2013-06-28 22:06:11 | Re: [GENERAL] pg_upgrade -u |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2013-06-28 23:21:18 | Re: [HACKERS] index refuses to build |
| Previous Message | Gilles Darold | 2013-06-28 23:08:16 | psql and pset without any arguments |