Re: Freezing without cleanup lock - Mailing list pgsql-hackers

From Andres Freund
Subject Re: Freezing without cleanup lock
Date
Msg-id 380530E1-91C6-4E99-A045-0EAFE8E872F1@anarazel.de
Whole thread Raw
In response to Re: Freezing without cleanup lock  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On October 21, 2015 9:47:45 PM GMT+02:00, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>Jim Nasby <Jim.Nasby@BlueTreble.com> writes:
>> While warning a client that just did a Slony-based version upgrade to
>
>> make sure to freeze the new database, it occurred to me that it
>should 
>> be safe to freeze without the cleanup lock.
>
>What's your argument for that being safe?

It doesn't affect tuple contents and thus backends having a pin can continue looking at tuple contents. The reason we
needa cleanup lock is IIRC repairing page fragmentation / hot pruning, not freezing.
 

Andres

--- 
Please excuse brevity and formatting - I am writing this on my mobile phone.



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Freezing without cleanup lock
Next
From: Euler Taveira
Date:
Subject: Re: Duplicated assignment of slot_name in walsender.c