Re: [HACKERS] BUG #2683: spi_exec_query in plperl returns - Mailing list pgsql-bugs

From Tom Lane
Subject Re: [HACKERS] BUG #2683: spi_exec_query in plperl returns
Date
Msg-id 20263.1161008886@sss.pgh.pa.us
Whole thread Raw
In response to BUG #2683: spi_exec_query in plperl returns column names which are not marked as UTF8  ("Vitali Stupin" <Vitali.Stupin@ria.ee>)
List pgsql-bugs
Martijn van Oosterhout <kleptog@svana.org> writes:
> It's clear whether you actually want to allow people to put utf8
> characters directly into their source (especially if the database is
> not in utf8 encoding anyway). There is always the \u{xxxx} escape.

Well, if the database encoding isn't utf8 then we'd not issue any such
command anyway.  But if it is, then AFAICS the text of pg_proc entries
could be expected to be utf8 too.
        regards, tom lane


pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #2694: Memory allocation error when selecting array of empty arrays
Next
From: "Paul Laughlin"
Date:
Subject: duplicate key violates unique constraint pg_toast_635216540