Which, doesn't work as expected as it seems as though there's
something
left behind on the stack that shouldn't be. Here's the case to
reproduce (doesn't involve pgmemcache):
test=# CREATE FUNCTION t5_func() RETURNS TRIGGER AS 'BEGIN EXECUTE
TRUE; RETURN NULL; END;' LANGUAGE 'plpgsql';
What are
Kent Tong <[EMAIL PROTECTED]> writes:
> You mean the OS fails to convert unicode strings to Big5 or the
> OS assumes the bytes are already in Big5?
The latter.
> It is the locale used for initdb or the default system locale
> set in Windows that is used by the collation routines that you
> mentio
Peter Eisentraut wrote:
On a POSIX system, you can do
$ LC_ALL= locale charmap
and verify manually that the printed charmap (= character set encoding)
matches what you use in PostgreSQL. I don't know whether an equivalent
interface exists on Windows.
Right, there is no such command.
Reading and
Sean Chittenden <[EMAIL PROTECTED]> writes:
> Which, doesn't work as expected as it seems as though there's something
> left behind on the stack that shouldn't be. Here's the case to
> reproduce (doesn't involve pgmemcache):
> test=# CREATE FUNCTION t5_func() RETURNS TRIGGER AS 'BEGIN EXECUTE
[snip] Err... wait, this is a classic case of send first then
finishing to pondering the gripe.
And sending a reply to ones self without actually testing my suggestion.
db=# CREATE FUNCTION schma.tbl_inval() RETURNS TRIGGER AS 'BEGIN
EXECUTE public.mc_init();
EXECUTE public.mc_del
"PostgreSQL Bugs List" <[EMAIL PROTECTED]> writes:
> With PGCLIENTENCODING=KOI8 and server encoding UNICODE
> psql do not starts and print this message:
> psql: FATAL: invalid value for parameter "client_encoding": "KOI8"
Found the problem ... it's something I broke last week :-(. It's fixed
n
"PostgreSQL Bugs List" <[EMAIL PROTECTED]> writes:
> With PGCLIENTENCODING=KOI8 and server encoding UNICODE
> psql do not starts and print this message:
> psql: FATAL: invalid value for parameter "client_encoding": "KOI8"
Odd ... it Works For Me:
$ PGCLIENTENCODING=KOI8 psql regression
Welcom
Kent Tong wrote:
> Is there any way to check?
On a POSIX system, you can do
$ LC_ALL= locale charmap
and verify manually that the printed charmap (= character set encoding)
matches what you use in PostgreSQL. I don't know whether an equivalent
interface exists on Windows.
> I have other prog
The following bug has been logged online:
Bug reference: 1328
Logged by: kaaos
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0 Beta
Operating system: Linux kaaos 2.6.9 #3 Tue Nov 23 13:12:08 MSK 2004 i686
Intel(R) Celeron(R) CPU 1.70GHz GenuineIntel GNU/Linux
D
Peter Eisentraut wrote:
Here is a test (run in pgadmin III):
1. createdb db1 -E Unicode
Probably your locale does not support Unicode. You need to pick an
encoding that matches your locale or vice versa.
Is there any way to check?
I have other programs reading and writing Unicode on this
compute
Kent Tong wrote:
> I'm running PostgreSQL v8 beta4 on Win2K. The default language
> selected in Win2K is Big5.
Big5 is an encoding, not a language.
> I am using the Windows installer to install it. Everything is
> left as default except that the locale for initdb is set to
> "traditional-chinese"
Hi,
I'm running PostgreSQL v8 beta4 on Win2K. The default language
selected in Win2K is Big5.
I am using the Windows installer to install it. Everything is
left as default except that the locale for initdb is set to
"traditional-chinese".
Here is a test (run in pgadmin III):
1. createdb db1 -E Unic
12 matches
Mail list logo
