Re: drop/truncate table sucks for large values of shared buffers - Mailing list pgsql-hackers

From Amit Kapila
Subject Re: drop/truncate table sucks for large values of shared buffers
Date
Msg-id CAA4eK1+8i7u4NAvQVNMYvH7i20Ue4Zg7FKXWjyLMRn9ryzHiMA@mail.gmail.com
Whole thread Raw
In response to Re: drop/truncate table sucks for large values of shared buffers  (Heikki Linnakangas <hlinnaka@iki.fi>)
List pgsql-hackers
On Thu, Jul 2, 2015 at 7:27 PM, Heikki Linnakangas <hlinnaka@iki.fi> wrote:
>
> On 07/02/2015 04:18 PM, Amit Kapila wrote:
>>
>>
>> Don't you think the approach discussed (delayed cleanup of buffers
>> during checkpoint scan) is sufficient to fix the issues raised.
>
>
> Dunno, but there is no patch for that.
>

That's fair enough, however your reply sounded to me like there is
no further need to explore this idea, unless we have something like
radix tree based approach.


With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com

pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: Reducing the size of BufferTag & remodeling forks
Next
From: Pavel Stehule
Date:
Subject: Re: raw output from copy