Skip site navigation (1) Skip section navigation (2)

Re: pg_upgrade fails for non-postgres user

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bernd Helmle <mailings(at)oopsware(dot)de>
Cc: Josh Berkus <josh(at)agliodbs(dot)com>, Magnus Hagander <magnus(at)hagander(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_upgrade fails for non-postgres user
Date: 2011-01-29 17:11:40
Message-ID: 12303.1296321100@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackers
Bernd Helmle <mailings(at)oopsware(dot)de> writes:
> --On 28. Januar 2011 14:49:21 -0800 Josh Berkus <josh(at)agliodbs(dot)com> wrote:
>> The database "postgres" is
>> reasonably likely to be dropped, whereas template1 doesn't get touched
>> usually.

> This is true for a bunch of installations i know. Maybe it's worth to make 
> it a command line switch to override the default behavior, too.

You're both forgetting that the new DB is freshly initdb'd.  It is
certain to contain a postgres database.

			regards, tom lane

In response to

pgsql-hackers by date

Next:From: Peter EisentrautDate: 2011-01-29 17:23:56
Subject: Re: REVIEW: Determining client_encoding from client locale
Previous:From: Stephen FrostDate: 2011-01-29 16:50:19
Subject: REVIEW: Determining client_encoding from client locale

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group