| From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>, Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [HACKERS] Assertion failure when the non-exclusive pg_stop_backup aborted. |
| Date: | 2017-12-18 03:31:26 |
| Message-ID: | CAB7nPqQDyTUMM-W7F0og4iMfYh3WwjaRn5dTBKoGfV1+eGhR6Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Dec 18, 2017 at 12:14 PM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> On Thu, Dec 14, 2017 at 7:51 PM, Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com> wrote:
>> +1 from me.
>
> Works for me, too, although I still don't really follow how it's
> happening in the present coding.
Craig has mentioned at least one way upthread:
https://www.postgresql.org/message-id/CAMsr+YHj4asAu8dJ1Q5hiW+wxL2Jd1=uxO52dvXhMxive-xd0g@mail.gmail.com
And that's possible when building with LOCK_DEBUG with trace_lwlocks
enabled at least. So I would rather not rely on assuming that
CHECK_FOR_INTERRUPTS() as a code path never taken for the cases
discussed here.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Masahiko Sawada | 2017-12-18 05:04:08 | Re: [HACKERS] Moving relation extension locks out of heavyweight lock manager |
| Previous Message | Robert Haas | 2017-12-18 03:14:50 | Re: [HACKERS] Assertion failure when the non-exclusive pg_stop_backup aborted. |