Re: [HACKERS] Backend crash on non-exclusive backup cancel - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: [HACKERS] Backend crash on non-exclusive backup cancel
Date
Msg-id CAB7nPqQ355viypxHKbD6Jt0FUktiV+B2LTSAwg1tO0qTga+VSQ@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] Backend crash on non-exclusive backup cancel  (Andres Freund <andres@anarazel.de>)
List pgsql-hackers
On Thu, Mar 16, 2017 at 12:46 AM, Andres Freund <andres@anarazel.de> wrote:
> Hi,
>
> On 2017-03-15 15:28:03 +0900, Michael Paquier wrote:
>> diff --git a/src/backend/access/transam/xlog.c b/src/backend/access/transam/xlog.c
>> index 64335f909e..eaf8e32fe1 100644
>> --- a/src/backend/access/transam/xlog.c
>> +++ b/src/backend/access/transam/xlog.c
>> --- a/src/backend/access/transam/xlogfuncs.c
>> +++ b/src/backend/access/transam/xlogfuncs.c
>> diff --git a/src/include/access/xlog.h b/src/include/access/xlog.h
>> index 104ee7dd5e..d4abf94862 100644
>> --- a/src/include/access/xlog.h
>> +++ b/src/include/access/xlog.h
>> @@ -288,8 +288,26 @@ extern void assign_max_wal_size(int newval, void *extra);
>>  extern void assign_checkpoint_completion_target(double newval, void *extra);
>
> This seems like something easy enough to exercise in a tap test, could
> we get one?

The first problem needs to have a cancel request sent when
pg_stop_backup() is running, the second needs to have a session held
to see an the inconsistent status of the session lock, which are two
concepts foreign to the TAP tests without being able to run the
queries asynchronously and keep the sessions alive.
-- 
Michael



pgsql-hackers by date:

Previous
From: David Rowley
Date:
Subject: Re: [HACKERS] Patch to improve performance of replay of AccessExclusiveLock
Next
From: Peter Eisentraut
Date:
Subject: Re: [HACKERS] logical replication access control patches