| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Stephen Frost <sfrost(at)snowman(dot)net>, Harold Giménez <harold(dot)gimenez(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: pg_upgrade improvements |
| Date: | 2012-04-05 13:34:56 |
| Message-ID: | CA+TgmobpUDUz3n7j01N97uoLukAsSqdJ-gajX2TAXZ5angquSA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Apr 4, 2012 at 11:56 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Stephen Frost <sfrost(at)snowman(dot)net> writes:
>> The single-user option *sounds* viable, but, iirc, it actually isn't due
>> to the limitations on what can be done in that mode.
>
> Yeah. IMO the right long-term fix is to be able to run pg_dump and psql
> talking to a standalone backend, but nobody's gotten round to making
> that possible.
Are you thinking about something like postgres --single
--port=PORT_NUMBER_OR_SOCKET_DIRECTORY?
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2012-04-05 13:46:54 | Re: pg_upgrade improvements |
| Previous Message | Greg Stark | 2012-04-05 13:29:22 | Re: patch: improve SLRU replacement algorithm |