| From: | Josh Kupershmidt <schmiddy(at)gmail(dot)com> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Magnus Hagander <magnus(at)hagander(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Default mode for shutdown |
| Date: | 2010-12-16 21:47:51 |
| Message-ID: | AANLkTimaMJywroj=Uj3y5iyn_tbCzj2sye6hLBjUBh7z@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Dec 15, 2010 at 10:11 AM, Alvaro Herrera
<alvherre(at)commandprompt(dot)com> wrote:
> It occurs to me that we may need a new mode, which disconnects sessions
> that are not in a transaction (or as soon as they are) but leaves
> in-progress transactions alone; this could be the new default. Of
> course, this is much more difficult to implement than the current modes.
I like this idea, if it's feasible. Might I also suggest that the
smart-mode shutdown give a HINT to the user that he can forcibly kill
off existing sessions using -m fast. Right now, we show something
like this:
$ pg_ctl -D PGDATA stop
waiting for server to shut down....
........................................................... failed
pg_ctl: server does not shut down
And it's not immediately obvious to the user why the server didn't
shut down, or how to fix things.
Josh
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2010-12-16 22:29:50 | Re: directory archive format for pg_dump |
| Previous Message | Dimitri Fontaine | 2010-12-16 21:47:18 | Re: Extensions, patch v18 (merge against master, bitrot-only-fixes) |