Re: Removing PD_ALL_VISIBLE - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Removing PD_ALL_VISIBLE
Date
Msg-id 5225.1358738342@sss.pgh.pa.us
Whole thread Raw
In response to Re: Removing PD_ALL_VISIBLE  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: Removing PD_ALL_VISIBLE
Re: Removing PD_ALL_VISIBLE
List pgsql-hackers
Robert Haas <robertmhaas@gmail.com> writes:
> On Fri, Jan 18, 2013 at 3:31 AM, Jeff Davis <pgsql@j-davis.com> wrote:
>> So, I attached a new version of the patch that doesn't look at the VM
>> for tables with fewer than 32 pages. That's the only change.

> That certainly seems worthwhile, but I still don't want to get rid of
> this code.  I'm just not seeing a reason why that's something that
> desperately needs to be done.

Yeah, I'm having the same problem.  Despite Jeff's test results, I can't
help thinking that lack of PD_ALL_VISIBLE *will* hurt us under some
workloads, and it's not obvious to me what benefit we get from dropping
it.
        regards, tom lane



pgsql-hackers by date:

Previous
From: Amit Kapila
Date:
Subject: Re: Re: Proposal for Allow postgresql.conf values to be changed via SQL [review]
Next
From: Robert Haas
Date:
Subject: Re: proposal: fix corner use case of variadic fuctions usage