| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Jeff Davis <pgsql(at)j-davis(dot)com>, Pavan Deolasee <pavan(dot)deolasee(at)gmail(dot)com>, Simon Riggs <simon(at)2ndquadrant(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Removing PD_ALL_VISIBLE |
| Date: | 2013-01-21 03:19:02 |
| Message-ID: | 5225.1358738342@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> On Fri, Jan 18, 2013 at 3:31 AM, Jeff Davis <pgsql(at)j-davis(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2013-01-21 03:23:19 | Re: proposal: fix corner use case of variadic fuctions usage |
| Previous Message | Amit Kapila | 2013-01-21 03:17:42 | Re: Re: Proposal for Allow postgresql.conf values to be changed via SQL [review] |