On 8 January 2013 18:46, Josh Berkus <josh(at)agliodbs(dot)com> wrote:
> On 1/5/13 1:21 PM, Peter Geoghegan wrote:
>> On 21 December 2012 14:08, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
>>> I'm sure it's possible; I don't *think* it's terribly easy.
>> I'm inclined to agree that this isn't a terribly pressing issue.
>> Certainly, the need to introduce a bunch of new infrastructure to
>> detect this case seems hard to justify.
> Impossible to justify, I'd say.
> Does anyone have any objections to my adding this to the TODO list, in case
> some clever GSOC student comes up with a way to do it *without* adding a
> bunch of infrastructure?
Daniel already did object....
I think we have other problems that need solving much more than this.
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
In response to
pgsql-hackers by date
|Next:||From: Tom Lane||Date: 2013-01-08 19:53:29|
|Subject: Re: [PATCH 2/5] Make relpathbackend return a statically result instead of palloc()'ing it|
|Previous:||From: Andres Freund||Date: 2013-01-08 19:37:00|
|Subject: Re: [PATCH 2/5] Make relpathbackend return a statically
result instead of palloc()'ing it|