Re: invalidly encoded strings - Mailing list pgsql-hackers

From Tom Lane
Subject Re: invalidly encoded strings
Date
Msg-id 12574.1189479628@sss.pgh.pa.us
Whole thread Raw
In response to Re: invalidly encoded strings  (Andrew Dunstan <andrew@dunslane.net>)
List pgsql-hackers
Andrew Dunstan <andrew@dunslane.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


pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: invalidly encoded strings
Next
From: Tom Lane
Date:
Subject: Re: invalidly encoded strings