| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Josh Berkus <josh(at)agliodbs(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andrew Dunstan <andrew(at)dunslane(dot)net>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: remove contrib/xml2 |
| Date: | 2010-01-29 00:31:17 |
| Message-ID: | 603c8f071001281631k74cd5d7ag1569d9a519f1384a@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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
do/don't work.
...Robert
| From | Date | Subject | |
|---|---|---|---|
| Next Message | KaiGai Kohei | 2010-01-29 00:58:46 | Re: [BUG?] strange behavior in ALTER TABLE ... RENAME TO on inherited columns |
| Previous Message | Robert Haas | 2010-01-29 00:29:27 | Re: [BUG?] strange behavior in ALTER TABLE ... RENAME TO on inherited columns |