Re: pg_upgrade using appname to lock out other users - Mailing list pgsql-hackers

From Tom Lane
Subject Re: pg_upgrade using appname to lock out other users
Date
Msg-id 13368.1308156750@sss.pgh.pa.us
Whole thread Raw
In response to Re: pg_upgrade using appname to lock out other users  (Alvaro Herrera <alvherre@commandprompt.com>)
Responses Re: pg_upgrade using appname to lock out other users
List pgsql-hackers
Alvaro Herrera <alvherre@commandprompt.com> writes:
> Excerpts from Robert Haas's message of mié jun 15 08:45:21 -0400 2011:
>> As a separate issue, I tend to agree with Tom that using psql as part
>> of the pg_upgrade process is a lousy idea and we need a better
>> solution.  But let's fix one thing at a time.

> Agreed on both counts ... but ... does this mean that we need a
> different program for programmable tasks as opposed to interactive
> ones?  Dealing with standalone backends *is* a pain, that's for sure.

So we fix the interface presented by standalone mode to be less insane.
That way, we can *reduce* the net amount of cruft in the system, rather
than adding more as all these proposals do.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: pg_upgrade using appname to lock out other users
Next
From: Peter Geoghegan
Date:
Subject: Re: bad posix_fadvise support causes initdb to exit ungracefully