| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pg_upgrade using appname to lock out other users |
| Date: | 2011-06-15 17:13:03 |
| Message-ID: | 1308157691-sup-4154@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| 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(at)commandprompt(dot)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(at)commandprompt(dot)com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2011-06-15 17:18:57 | Re: pg_upgrade using appname to lock out other users |
| Previous Message | Tom Lane | 2011-06-15 17:12:45 | Re: bad posix_fadvise support causes initdb to exit ungracefully |