diff options
author | Bruce Momjian <bruce@momjian.us> | 2005-06-15 00:35:16 +0000 |
---|---|---|
committer | Bruce Momjian <bruce@momjian.us> | 2005-06-15 00:35:16 +0000 |
commit | d0925244189a9888d48a86b15e73ee8c4b3f82bb (patch) | |
tree | 2a75f81823b9026c3fbe88ae162e8635b52cfea1 /src/backend/access/gist/gist.c | |
parent | 0851a6fbc77e7f1762a2a94d370492f03450e922 (diff) | |
download | postgresql-d0925244189a9888d48a86b15e73ee8c4b3f82bb.tar.gz postgresql-d0925244189a9888d48a86b15e73ee8c4b3f82bb.zip |
> Here's a patch I added against plperl, originally against beta5, now
> against rc1. It simply checks with GetDatabaseEncoding() if the current
> database is in UTF-8, and if so, sets the UTF-8 flag on the arguments
> that are passed to perl. This means that it isn't necessary to
> utf8::upgrade() every string, as perl has no way of knowing offhand
> that a string is UTF-8 -- but postgres does, because the database
> encoding is specified, so it makes sense to turn the flag on. You
> should also be able to properly manipulate UTF-8 strings now from
> plperl as opposed to plperlu, because otherwise you'd have to use
> encoding 'utf8' which was not allowed. It could also eliminate some
> unexpected bugs if you assume that perl knows the string is unicode.
It
> is enabled only for perl 5.6 and higher, so earlier versions will not
> be affected.
>
> I have been assured by crab that the patch is quite harmless and will
> not break anything. It would be great to see it in 8 final! :-)
David Kamholz
Diffstat (limited to 'src/backend/access/gist/gist.c')
0 files changed, 0 insertions, 0 deletions