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

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: drop/truncate table sucks for large values of shared buffers
Date: 2015-06-28 13:57:52
Message-ID: 558FFD60.6010804@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


On 06/27/2015 10:10 AM, Tom Lane wrote:
> It also
> offers no hope of a fix for the other operations that scan the whole
> buffer pool, such as DROP TABLESPACE and DROP DATABASE.
>

Improving DROP TABLE / TRUNCATE would still be a significant advance.
These cases cause far more real world pain than the ones you mention, in
my experience.

cheers

andrew

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2015-06-28 14:01:13 Re: drop/truncate table sucks for large values of shared buffers
Previous Message David G. Johnston 2015-06-28 13:21:36 Re: proposal: condition blocks in psql