[BUGS] BUG #3413: character string or multibyte character to "char"

2007-06-26 Thread Toru SHIMOGAKI
The following bug has been logged online: Bug reference: 3413 Logged by: Toru SHIMOGAKI Email address: [EMAIL PROTECTED] PostgreSQL version: 8.2.4 Operating system: Red Hat Enterprise Linux AS4 Description:character string or multibyte character to "char" Details: W

Re: [BUGS] BUG #3413: character string or multibyte character to "char"

2007-06-26 Thread Toru SHIMOGAKI
This is a sample patch for charin() and charrecv(). I'm not sure for charout(); it can return non-ASCII character... Toru SHIMOGAKI wrote: > The following bug has been logged online: > > Bug reference: 3413 > Logged by: Toru SHIMOGAKI > Email address: [EMAIL PROTECTED] > Post

Re: [BUGS] REVOKE CREATE does not work on default tablespace

2007-06-26 Thread Zdenek Kotala
Tom Lane wrote: Zdenek Kotala <[EMAIL PROTECTED]> writes: Tom Lane wrote: It's presumed that the right to create tables within a database entails the right to create them someplace; hence no permissions check is made on the database's default tablespace. Without that, not only does plain CREAT

Re: [BUGS] BUG #3413: character string or multibyte character to "char"

2007-06-26 Thread Tom Lane
"Toru SHIMOGAKI" <[EMAIL PROTECTED]> writes: > When a character string or a multibyte character is inserted to "char" > column, no error occurs. Is this a bug? That's the historical behavior of the datatype, and given that it's been like that since Berkeley days, changing it seems ill-advised. If

Re: [BUGS] REVOKE CREATE does not work on default tablespace

2007-06-26 Thread Tom Lane
Zdenek Kotala <[EMAIL PROTECTED]> writes: > I still does not see any benefit from user side why postgres has this > exception. It is confusing and it should generate potential security > risk. "Security risk"? Now you're just making things up. regards, tom lane

[BUGS] PL/pgSQL RAISE EXCEPTION ignores escape characters even with new E'' string syntax

2007-06-26 Thread Donald Fraser
PostgreSQL 8.1.9 According to the release notes, PostgreSQL still handles escape characters in strings as it has in the past, yet PL/pgSQL functions that use escape characters within the string definition for RAISE EXCEPTION are ignored, unless the function is created using the old style quote

Re: [BUGS] PL/pgSQL RAISE EXCEPTION ignores escape characters even with new E'' string syntax

2007-06-26 Thread Tom Lane
"Donald Fraser" <[EMAIL PROTECTED]> writes: > According to the release notes, PostgreSQL still handles escape = > characters in strings as it has in the past, yet PL/pgSQL functions that = > use escape characters within the string definition for RAISE EXCEPTION = > are ignored, unless the function

[BUGS] BUG #3414: client-only install fails due to parse.h file not found

2007-06-26 Thread Geoff Taylor
The following bug has been logged online: Bug reference: 3414 Logged by: Geoff Taylor Email address: [EMAIL PROTECTED] PostgreSQL version: 8.1.9 Operating system: Redhat Linux Description:client-only install fails due to parse.h file not found Details: I tried the c

[BUGS] BUG #3415: plperl spi_exec_prepared variable undef value confusion

2007-06-26 Thread Matt
The following bug has been logged online: Bug reference: 3415 Logged by: Matt Email address: [EMAIL PROTECTED] PostgreSQL version: 8.2.3 Operating system: ubuntu 7.04, gentoo 2007.0 Description:plperl spi_exec_prepared variable undef value confusion Details: When in