| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | Tatsuo Ishii <ishii(at)postgresql(dot)org>, laurenz(dot)albe(at)wien(dot)gv(dot)at, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: invalidly encoded strings |
| Date: | 2007-09-11 03:00:28 |
| Message-ID: | 12574.1189479628@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> I'm not sure we are going to be able to catch every path by which
> invalid data can get into the database in one release. I suspect we
> might need two or three goes at this. (I'm just wondering if the
> routines that return cstrings are a possible vector).
We need to have a policy that cstrings are in the database encoding.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2007-09-11 03:20:02 | Re: invalidly encoded strings |
| Previous Message | Andrew Dunstan | 2007-09-11 02:55:57 | Re: invalidly encoded strings |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2007-09-11 03:20:02 | Re: invalidly encoded strings |
| Previous Message | Andrew Dunstan | 2007-09-11 02:55:57 | Re: invalidly encoded strings |