Re: Index maintenance function for BRIN doesn't check RecoveryInProgress() - Mailing list pgsql-hackers

From Alexander Korotkov
Subject Re: Index maintenance function for BRIN doesn't check RecoveryInProgress()
Date
Msg-id CAPpHfdsZPy-Qnco1h1we-ub0pjP8Bdvohk8A3zm33RxRfkRURw@mail.gmail.com
Whole thread Raw
In response to Re: Index maintenance function for BRIN doesn't check RecoveryInProgress()  (Kuntal Ghosh <kuntalghosh.2007@gmail.com>)
Responses Re: Index maintenance function for BRIN doesn't checkRecoveryInProgress()
List pgsql-hackers
On Wed, Jun 13, 2018 at 12:48 PM Kuntal Ghosh
<kuntalghosh.2007@gmail.com> wrote:
> On Wed, Jun 13, 2018 at 2:28 PM, Masahiko Sawada <sawada.mshk@gmail.com> wrote:
> > Hi,
> >
> > Three functions: brin_summarize_new_values, brin_summarize_range and
> > brin_desummarize_range can be called during recovery as follows.
> >
> > =# select brin_summarize_new_values('a_idx');
> > ERROR:  cannot acquire lock mode ShareUpdateExclusiveLock on database
> > objects while recovery is in progress
> > HINT:  Only RowExclusiveLock or less can be acquired on database
> > objects during recovery.
> >
> > I think we should complaint "recovery is in progress" error in this
> > case rather than erroring due to lock modes.
> +1

+1,
but current behavior doesn't seem to be bug, but rather not precise
enough error reporting.  So, I think we shouldn't consider
backpatching this.

------
Alexander Korotkov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company


pgsql-hackers by date:

Previous
From: Marina Polyakova
Date:
Subject: Re: [HACKERS] WIP Patch: Pgbench Serialization and deadlock errors
Next
From: David Rowley
Date:
Subject: Partitioning with temp tables is broken