Re: pg_upgrade using appname to lock out other users

Alvaro Herrera <alvherre@commandprompt.com>

From: Alvaro Herrera <alvherre@commandprompt.com>

To: Robert Haas <robertmhaas@gmail.com>

Cc: Bruce Momjian <bruce@momjian.us>, Tom Lane <tgl@sss.pgh.pa.us>, PostgreSQL-development <pgsql-hackers@postgresql.org>

Date: 2011-06-15T17:13:03Z

Lists: pgsql-hackers

Excerpts from Robert Haas's message of mié jun 15 12:51:29 -0400 2011:
> On Wed, Jun 15, 2011 at 12:12 PM, Alvaro Herrera
> <alvherre@commandprompt.com> wrote:

> > 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.
> 
> I'm not sure exactly what is needed here - what programmable tasks are
> you thinking of, other than pg_upgrade?

Well, something to use on shell scripts and the like first and foremost;
see 
http://petereisentraut.blogspot.com/2010/03/running-sql-scripts-with-psql.html

-- 
Álvaro Herrera <alvherre@commandprompt.com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support