[BUGS] BUG #1233: JDBC driver: moveToCurrentRow fails

The following bug has been logged online: Bug reference: 1233 Logged by: David Bucciarelli Email address: [EMAIL PROTECTED] PostgreSQL version: 7.4.3 Operating system: Linux Suse 9.0 Description:JDBC driver: moveToCurrentRow fails Details: The method moveToCurr

[BUGS] BUG #1234: prepared statements and libpq don't work as expected

The following bug has been logged online: Bug reference: 1234 Logged by: Sven Riedel Email address: [EMAIL PROTECTED] PostgreSQL version: 8.0 Beta Operating system: Linux, Kernel 2.6 Description:prepared statements and libpq don't work as expected Details: Hi,

[BUGS] BUG #1235: didn't compile

The following bug has been logged online: Bug reference: 1235 Logged by: oliver artelt Email address: [EMAIL PROTECTED] PostgreSQL version: 8.0 Beta Operating system: Linux baldur 2.4.10 #1 SMP Wed Aug 7 13:37:21 CEST 2002 i686 unknown Description:didn't compile

Re: [BUGS] BUG #1234: prepared statements and libpq don't work as expected

"PostgreSQL Bugs List" <[EMAIL PROTECTED]> writes: > The code in question looks like this: > static const char *prepareuserquery = >"PREPARE UserQuery (text,text) AS SELECT UserID FROM Users WHERE Name=$1 > AND Password=$2"; > if( ( result = PQexecPrepared( sqlhandle, "UserQuery", 2,

Re: [BUGS] BUG #1235: didn't compile

"PostgreSQL Bugs List" <[EMAIL PROTECTED]> writes: > syslogger.c: In function `SysLoggerMain': > syslogger.c:231: storage size of `timeout' isn't known > syslogger.c:231: warning: unused variable `timeout' > make[3]: *** [syslogger.o] Error 1 This is fixed. http://developer.postgresql.org/cvsweb.

Re: [BUGS] BUG #1231: Probelm with transactions in stored code.

On Thu, 2004-08-26 at 09:08, Gaetano Mendola wrote: > Robert Treat wrote: > > > On Thu, 2004-08-26 at 04:23, Gaetano Mendola wrote: > > > >>Tom Lane wrote: > >> > >> > Stephan Szabo <[EMAIL PROTECTED]> writes: > >> > > >> >>I believe it sees the one that was valid in the snapshot as of the > >> >

Re: [BUGS] BUG #1231: Probelm with transactions in stored code.

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Robert Treat wrote: | On Thu, 2004-08-26 at 09:08, Gaetano Mendola wrote: | |>Robert Treat wrote: |> |> |>>On Thu, 2004-08-26 at 04:23, Gaetano Mendola wrote: |>> |>> |>>>Tom Lane wrote: |>>> |>>> |Stephan Szabo <[EMAIL PROTECTED]> writes: | |>>

Re: [BUGS] BUG #1231: Probelm with transactions in stored code.

Robert Treat wrote: On Thu, 2004-08-26 at 09:08, Gaetano Mendola wrote: Robert Treat wrote: On Thu, 2004-08-26 at 04:23, Gaetano Mendola wrote: Tom Lane wrote: Stephan Szabo <[EMAIL PROTECTED]> writes: I believe it sees the one that was valid in the snapshot as of the beginning of the function.

Re: [BUGS] replacing a function called "isnull" reports an error

Thanks Tom, I'm trying to drop the function and it's giving a similar message that the function cannot be dropped ... I have supposed that "isnull" was a reserved word, but the system could not accept to create a function if it cannot drop it (I guess). Thanks again. --- Tom Lane <[EMAIL PROTEC

[BUGS] pgsql 8.0 beta1 patch for token and timezone

Hi pgsql-bugs, I'm a Chinese and I am using WinXp Chs to compile pgsql 8.0 beta 1 in the MinGW environment. I found 2 bugs and fix them, maybe you can merge the patch into the offical release, thanks. Part A) Below is the two bugs occur when we run initdb under WinXp Chs. 1) FATAL: syntax er

[BUGS] Postgres 8.0.0beta1 didn't compile

Hi, Postgres 8.0.0beta1 didn't compile on an older linux machine: /configure --prefix /usr/local/pgsql-8.0.0beta1 make .. syslogger.c: In function `SysLoggerMain': syslogger.c:231: storage size of `timeout' isn't known syslogger.c:231: warning: unused variable `timeout' make[3]: *** [syslogger

[BUGS] Apologies if you don't consider this a bug and I've wasted your time.

Hi, I have a postgresql database that I have added postgis capabilities to. When I pg_dump out the database, it outputs all the tables, functions, types as you'd expect, but it outputs table definitions that reference postgis functions/types *before* the functions/types themselves. This means

[BUGS] initdb errors, postgresql-8.0-beta

POSTGRESQL BUG REPORT TEMPLATE Your name : Murthy Your email address : [EMAIL PROTECTED] System C

[BUGS] pgsql 8.0 beta1 patch for token and timezone

Hi pgsql-bugs-owner, I want to join the bug mailing list cauz I found 2 bugs and fixed them. Regards, Jacky -> From: [EMAIL PROTECTED] To: "Zhong Jacky" <[EMAIL PROTECTED]> Subject: Stalled post to pgsql-bugs Date: Wed, 25 Aug 2004 23:43:48 -0300 Your message t

[BUGS] Postgres 8.0.0b1 build on Solaris 10 Ultrasparc

hello all, here follows the regression test run on postgres 8.0.0b1. Hardware Ultra 2 dual 300MHz CPUS 768MB RAM OS Solaris 10 b 5 -- == creating temporary installation== == initializing database system ===

Re: [BUGS] Memory leak

Tom, I am not sure if my original message made it onto a forum or knowledge base but I was wondering if it would be possible for you to take it down if it is? There may potentially be some sensitive information in it. Thanks -Original Message- From: Tom Lane [mailto:[EMAIL PROTECT

Re: [BUGS] Postgres 8.0/Windows 2000 Load testing

The problem is not only with Postgres 8.0,. It happens with 7.2.x,(cygipc), 7.4.x(cygserver) version as well. But with the previous versions atleast the test was able to last a for 5-6 concurrent connections. But with 8.0, with 3-4 concurrent connection itself it starts to break. On Linux(wi

Re: [BUGS] Apologies if you don't consider this a bug and I've wasted your time.

Steve Ingram <[EMAIL PROTECTED]> writes: > When I pg_dump out the database, it outputs all the tables, functions, types > as you'd expect, but it outputs table definitions that reference postgis > functions/types *before* the functions/types themselves. Yeah, this is pretty likely if you did any A