Re: drop/truncate table sucks for large values of shared buffers

From: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
To: hlinnaka <hlinnaka(at)iki(dot)fi>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: drop/truncate table sucks for large values of shared buffers
Date: 2015-07-02 14:08:42
Message-ID: CAA4eK1+8i7u4NAvQVNMYvH7i20Ue4Zg7FKXWjyLMRn9ryzHiMA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Jul 2, 2015 at 7:27 PM, Heikki Linnakangas <hlinnaka(at)iki(dot)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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Kouhei Kaigai 2015-07-02 14:13:36 Re: Foreign join pushdown vs EvalPlanQual
Previous Message Heikki Linnakangas 2015-07-02 14:07:47 Fwd: A better translation version of Chinese for psql/po/zh_CN.po file