| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Mark Dilger <mark(dot)dilger(at)enterprisedb(dot)com> |
| Cc: | Amul Sul <sulamul(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com>, Dilip Kumar <dilipbalaut(at)gmail(dot)com>, Ibrar Ahmed <ibrar(dot)ahmad(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Prabhat Sahu <prabhat(dot)sahu(at)enterprisedb(dot)com> |
| Subject: | Re: [Patch] ALTER SYSTEM READ ONLY |
| Date: | 2021-09-10 17:48:14 |
| Message-ID: | CA+Tgmoa=4sT8m-O-a6iEUPQiP1-0jAOwVri5xkSYdSXvvDuVbg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Sep 10, 2021 at 1:16 PM Mark Dilger
<mark(dot)dilger(at)enterprisedb(dot)com> wrote:
> uses "immediately" and "will kill the running transaction" which reenforced the impression that this mechanism is heavier handed than it is.
It's intended to be just as immediate as e.g. pg_cancel_backend() and
pg_terminate_backend(), which work just the same way, but not any more
so. I guess we could look at how things are worded in those cases.
From a user perspective such things are usually pretty immediate, but
not as immediate as firing a signal handler. Computers are fast.[1]
--
Robert Haas
EDB: http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Justin Pryzby | 2021-09-10 17:56:08 | Re: incorrect file name in backend_progress.c header |
| Previous Message | Robert Haas | 2021-09-10 17:42:06 | Re: parallelizing the archiver |