| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Josh Berkus <josh(at)agliodbs(dot)com>, 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 03:00:50 |
| Message-ID: | 20100129030050.GB1793@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Robert Haas escribió:
> 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.
If it were easy to throw an error, it'd be better to avoid the crash.
--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | KaiGai Kohei | 2010-01-29 03:02:22 | Re: [BUG?] strange behavior in ALTER TABLE ... RENAME TO on inherited columns |
| Previous Message | Alvaro Herrera | 2010-01-29 02:59:22 | Re: Pathological regexp match |