"Michael Andreen" <[EMAIL PROTECTED]> writes:
> CREATE OR REPLACE FUNCTION crash()
> RETURNS int4 AS
> $BODY$$rv = spi_exec_query("SELECT 1");
> $query = spi_prepare('SELECT 1 WHERE 1 = $1','integer');
> return 1;$BODY$
> LANGUAGE 'plperl' VOLATILE;
Thanks for the test case. This is not plper
Ross Cohen <[EMAIL PROTECTED]> writes:
> On Wed, Dec 06, 2006 at 05:55:32PM -0500, Tom Lane wrote:
>> "Ross Cohen" <[EMAIL PROTECTED]> writes:
>>> PREPARE demo (unknown) AS SELECT 1;
>>> ERROR: could not determine data type of parameter $1
>>
>> This doesn't seem like a bug to me. The parser nee
On Wed, Dec 06, 2006 at 05:55:32PM -0500, Tom Lane wrote:
> "Ross Cohen" <[EMAIL PROTECTED]> writes:
> > PREPARE demo (unknown) AS SELECT 1;
> > ERROR: could not determine data type of parameter $1
>
> This doesn't seem like a bug to me. The parser needs to be able to
> resolve the types of any
Thank you for your help and prompt response.
Regards,
Alex
-Original Message-
From: Alvaro Herrera [mailto:[EMAIL PROTECTED]
Sent: Wednesday, December 06, 2006 5:43 PM
To: Piyevsky, Alex
Cc: pgsql-bugs@postgresql.org
Subject: Re: [BUGS] BUG #2812: Transaction is aborted after error
Alex
Was playing around with the new release and changing some pl/perl
functions to use the new spi_prepare and friends when I noticed
postgresql terminating strangely, with no useful warnings at all, the
log contained the following:
Dec 7 16:58:28 [postgres] [7-1] LOG: database system is ready
De
The following bug has been logged online:
Bug reference: 2813
Logged by: Markus Grabner
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.2
Operating system: SuSE Linux 10.0, kernel 2.6.13-15.12-default. i586
Description:missing RPM build dependency: tcl-devel
De
The following bug has been logged online:
Bug reference: 2817
Logged by: Michael Andreen
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.2
Operating system: Gentoo Linux (unofficial postgresql 8.2 package)
Description:Mixing spi_prepare and spi_exec_query cause
"Ross Cohen" <[EMAIL PROTECTED]> writes:
> Description:constraint violation
Thanks for the report. I've applied a patch that I believe fixes this
... at least, it fixes Jeff Davis' test case.
regards, tom lane
---(end of broadcast)
"Joost Karaaijeveld" <[EMAIL PROTECTED]> writes:
> Printing a timestamp using '%t%' in Windows omits the timezone in the
> logfile. In Linux the timezone is printed. Either make the two the same by
> default or make it configurable so that the user can make them the same.
The zone name available f
The following bug has been logged online:
Bug reference: 2816
Logged by: Joost Karaaijeveld
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.5
Operating system: Windows 2000 / Linux Debian Etch
Description:Logfile difference in timestamp between Windows and
Li
10 matches
Mail list logo
