| From: | Greg Stark <stark(at)mit(dot)edu> |
|---|---|
| To: | Wolfgang Wilhelm <wolfgang20121964(at)yahoo(dot)de> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Simon Riggs <simon(at)2ndquadrant(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Magnus Hagander <magnus(at)hagander(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: smart shutdown at end of transaction (was: Default mode for shutdown) |
| Date: | 2012-04-30 12:53:28 |
| Message-ID: | CAM-w4HN7+zqK4rveK=eUWaM2HVbBCwD5zbzYxNMOhWaT0gEBQg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Apr 30, 2012 at 9:55 AM, Wolfgang Wilhelm
<wolfgang20121964(at)yahoo(dot)de> wrote:
> Just for the ones interested in a view on another turf:
>
> In Oracle "shutdown immediate" is the fastest _clean_ shutdown and "shutdown
> abort" is equal to "shutdown immediate" in PG.
> The other modes are called "shutdown normal" and "shutdown transactional".
Though the behaviour users see is quite different. In Oracle the
fastest clean shutdown still requires rolling back transactions which
can take a long time. In Postgres rolling back transactions is
instantaneous so a shutdown immediate will appear to behave like a
shutdown abort in Oracle in that it will always run fast even if the
effect on the database is different.
--
greg
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2012-04-30 13:02:33 | Re: [PATCH] Allow breaking out of hung connection attempts |
| Previous Message | Atri Sharma | 2012-04-30 12:00:07 | Re: Future In-Core Replication |