| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: WIP fix proposal for bug #6123 |
| Date: | 2011-07-25 16:57:07 |
| Message-ID: | CA+Tgmobrjkt+1dr8tzpL-oS0OtL9gNWBR4HyHp1=35coUf+Lrg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Jul 25, 2011 at 12:26 PM, Kevin Grittner
<Kevin(dot)Grittner(at)wicourts(dot)gov> wrote:
> There's no doubt that it would be better the way you're suggesting;
> but it looks to me like about five times as many lines of code,
> harder to be sure it's right, and probably forcing me to learn a few
> new subsystems of PostgreSQL internals to accomplish.
Sorry, I didn't mean to make homework for you. Nor am I sure that the
solution will pass must all around even if I think it's the best thing
since sliced bread. I was just throwing it out there as what I would
like to have happen in an ideal world...
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Florian Pflug | 2011-07-25 17:07:50 | Re: Another issue with invalid XML values |
| Previous Message | Bernd Helmle | 2011-07-25 16:53:13 | Re: Another issue with invalid XML values |