Postgres Pro
Downloads
Home   >   mailing lists

Re: Hot Standby WAL reply uses heavyweight session locks, but doesn't have enough infrastructure set up - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Hot Standby WAL reply uses heavyweight session locks, but doesn't have enough infrastructure set up
Date
Msg-id CA+TgmoZYiEJW5r+HFkokqptfr56i-eOCBu3QXxUdYDvNAV3eQw@mail.gmail.com
Whole thread Raw
In response to Re: Hot Standby WAL reply uses heavyweight session locks, but doesn't have enough infrastructure set up  (Michael Paquier <michael.paquier@gmail.com>)
Responses Re: Hot Standby WAL reply uses heavyweight session locks, but doesn't have enough infrastructure set up
List pgsql-hackers
Tree view 
On Wed, Jan 28, 2015 at 2:41 AM, Michael Paquier
<michael.paquier@gmail.com> wrote:
> Andres Freund wrote:
>> I think this isn't particularly pretty, but it seems to be working well
>> enough, and changing it would be pretty invasive. So keeping in line
>> with all that code seems to be easier.
> OK, I'm convinced with this part to remove the call of
> LockSharedObjectForSession that uses dontWait and replace it by a loop
> in ResolveRecoveryConflictWithDatabase.

That seems right to me, too.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

pgsql-hackers by date:

Previous
From: Marco Nenciarini
Date:
Subject: pg_check_dir comments and implementation mismatch
Next
From: Robert Haas
Date:
Subject: Re: TABLESAMPLE patch