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

From Tom Lane
Subject Re: drop/truncate table sucks for large values of shared buffers
Date
Msg-id 14561.1435845813@sss.pgh.pa.us
Whole thread Raw
In response to Re: drop/truncate table sucks for large values of shared buffers  (Simon Riggs <simon@2ndQuadrant.com>)
Responses Re: drop/truncate table sucks for large values of shared buffers
List pgsql-hackers
Simon Riggs <simon@2ndQuadrant.com> writes:
> On 2 July 2015 at 14:08, Heikki Linnakangas <hlinnaka@iki.fi> wrote:
>> I'm marking this as "returned with feedback" in the commitfest.

> There are no unresolved issues with the approach, nor is it true it is
> slower. If you think there are some, you should say what they are, not act
> high handedly to reject a patch without reason.

Have you read the thread?  There were plenty of objections, as well as
a design for a better solution.  In addition, we should think about
more holistic solutions such as Andres' nearby proposal (which I doubt
will work as-is, but maybe somebody will think of how to fix it).
Committing a band-aid will just make it harder to pursue real fixes.
        regards, tom lane



pgsql-hackers by date:

Previous
From: "Syed, Rahila"
Date:
Subject: Re: [PROPOSAL] VACUUM Progress Checker.
Next
From: Andres Freund
Date:
Subject: Re: Reducing the size of BufferTag & remodeling forks