From: | "Christopher Kings-Lynne" <chris(at)kkl(dot)com(dot)au> |
---|---|
To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | "Peter Eisentraut" <peter_e(at)gmx(dot)net>, "Nikolay Samokhvalov" <samokhvalov(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Loose ends in PG XML patch |
Date: | 2007-01-03 06:08:33 |
Message-ID: | 1acfe1a40701022208x4a280223k127dd57467863bb8@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers pgsql-hackers |
> * Shouldn't the xml type support binary I/O? Right now it is the only
> standard datatype that doesn't. I have no idea whether there is an
> appropriate representation besides text, but if not we could define the
> binary representation to be the same as text.
There is an effort to develop a binary xml format:
From | Date | Subject | |
---|---|---|---|
Next Message | User Okbob | 2007-01-03 09:55:38 | plpsm - plpgpsm: more consist behave of SQLSTATE |
Previous Message | Bruce Momjian | 2007-01-03 04:21:47 | pgsql: For float4/8, remove errno checks for pow() and exp() because |
From | Date | Subject | |
---|---|---|---|
Next Message | Jeremy Drake | 2007-01-03 06:14:03 | contrib regression failures after recent money type changes |
Previous Message | Jim C. Nasby | 2007-01-03 03:38:21 | Re: Sync Scan update |