On Thu, Jan 28, 2010 at 5:54 PM, Josh Berkus <j...@agliodbs.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 do/don't work. ...Robert -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
