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
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
"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
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
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
"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
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
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
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
