On Thu, Jan 28, 2010 at 5:54 PM, Josh Berkus <josh(at)agliodbs(dot)com> wrote:
>> Yeah, we can't really remove it until we have a plausible substitute for
>> the xpath_table functionality. This is in the TODO list ...
> What about moving it to pgfoundry?
> I'm really not keen on shipping known-broken stuff in /contrib.
Yeah, exactly. Another option - if we know that it works OK with
inputs of certain types - might be to throw an error if we get an
input of a type we know it doesn't work with. But I guess I haven't
followed this closely enough to know exactly what kinds of arguments
In response to
pgsql-hackers by date
|Next:||From: KaiGai Kohei||Date: 2010-01-29 00:58:46|
|Subject: Re: [BUG?] strange behavior in ALTER TABLE ... RENAME TO
on inherited columns|
|Previous:||From: Robert Haas||Date: 2010-01-29 00:29:27|
|Subject: Re: [BUG?] strange behavior in ALTER TABLE ... RENAME TO on inherited columns|