> I have just noticed that the implementation of > CONVERT(text USING encoding_name) > tries to do database access during the grammar phase, viz it looks > up the encoding_name in pg_conversion and replaces it with an OID. > > This is not workable; consider the situation where we are in an > already-aborted transaction. Using a pg_conversion OID in stored rules > isn't very acceptable either. > > Unfortunately, I don't see any way offhand to fix this without an > initdb :-(.
Sorry for the trouble and thanks for the fix. -- Tatsuo Ishii ---------------------------(end of broadcast)--------------------------- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
