| From: | Ray Stell <stellr(at)vt(dot)edu> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgreSQL(dot)org> |
| Subject: | Re: [GENERAL] pg_upgrade -u |
| Date: | 2013-05-30 12:42:21 |
| Message-ID: | 39CAC308-CE20-410B-A4F5-810438C04E0A@vt.edu |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general 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 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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Luca Ferrari | 2013-05-30 12:45:49 | Re: BLOB updates -> database size explodes |
| Previous Message | Benedikt Grundmann | 2013-05-30 09:37:34 | Re: How to upgrade postgres 8.4 -> 9.1 contrib? |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephen Frost | 2013-05-30 12:47:48 | Re: fallocate / posix_fallocate for new WAL file creation (etc...) |
| Previous Message | Andres Freund | 2013-05-30 12:39:30 | Re: removing PD_ALL_VISIBLE |