Re: [BUGS] currval and nextval in 7.3.4

2003-10-23 Thread Stephan Szabo
On Thu, 23 Oct 2003, Keith Marr wrote: > Hi, > > I recently installed 7.3.4 (complete install from scratch) and both 'select > nextval('my_seq') from my_table' and 'select currval('my_seq') from my_table' > return a number of rows equal to the number of rows in the table. > > The sequence was crea

[BUGS] ECPG and NULL indicators

2003-10-23 Thread Edmund Bacon
POSTGRESQL BUG REPORT Your name : Edmund Bacon Your email address : ebacon (at) onesyst

Re: [BUGS] my postgreSQL 7.4 beta for windows

2003-10-23 Thread Richard Huxton
On Wednesday 22 October 2003 05:07, dedy setiawan wrote: > hello,... > I'm using postgreSQL 7.4 beta for windows, and i use > them in my project with delphi and i use DBexpress for > connecting to then Postgres, but in other case my > postgres runs very slowly Could you subscribe to the performan

[BUGS] currval and nextval in 7.3.4

2003-10-23 Thread Keith Marr
Hi, I recently installed 7.3.4 (complete install from scratch) and both 'select nextval('my_seq') from my_table' and 'select currval('my_seq') from my_table' return a number of rows equal to the number of rows in the table. The sequence was created with a SERIAL type if that helps. In 'psql'

[BUGS] my postgreSQL 7.4 beta for windows

2003-10-23 Thread dedy setiawan
hello,... I'm using postgreSQL 7.4 beta for windows, and i use them in my project with delphi and i use DBexpress for connecting to then Postgres, but in other case my postgres runs very slowly ,I compare it with mySQL is faster than mine, By the way my computer spesification is : Intel PIII 600B

[BUGS] Behavior at odds with documentation (CREATE USER and SQL language functions)

2003-10-23 Thread Christopher Travers
Hi all; I came across another piece of strange behavior that I wanted to report to you. This appears to be related to previous email disucssions (see http://archives.postgresql.org/pgsql-bugs/2003-04/msg00091.php). Utility statements do not work from SQL language functions. Presumably this i

Re: [BUGS] BUG: PLPGSQL function causes PgSQL process to die when inserting into

2003-10-23 Thread Christopher Travers
My bad; As Tom has pointed out this is a known issue. Thanks. I wonder why my first search didn't find it (probably a typo on my part) :( Best Wishes. _ Try MSN Messenger 6.0 with integrated webcam functionality! http://www.msnm

Re: [BUGS] BUG: PLPGSQL function causes PgSQL process to die when inserting into

2003-10-23 Thread Tom Lane
"Christopher Travers" <[EMAIL PROTECTED]> writes: > Sorry, forgot the version information: 7.3.2 Update to 7.3.4 --- I see this fix in the CVS logs: 2003-02-14 16:12 tgl * src/backend/executor/spi.c (REL7_3_STABLE): Fix SPI result logic for case where there are multiple statemen

Re: [BUGS] BUG: PLPGSQL function causes PgSQL process to die when inserting into

2003-10-23 Thread Christopher Travers
Sorry, forgot the version information: 7.3.2 Full schema and example: CREATE TABLE owners_admin ( owner_id integer DEFAULT nextval('"owners_owner_id_seq"'::text) NOT NULL, first_name character varying(15) DEFAULT '', last_name character varying(15) DEFAULT '', login character varying

Re: [BUGS] BUG: PLPGSQL function causes PgSQL process to die when inserting into a view

2003-10-23 Thread Tom Lane
"Christopher Travers" <[EMAIL PROTECTED]> writes: > FATAL: SPI: improper call to spi_dest_setup I think this is a known and already-fixed bug. What version are you running? regards, tom lane ---(end of broadcast)--- TIP 3:

Re: [BUGS] BUG: PLPGSQL function causes PgSQL process to die when

2003-10-23 Thread Stephan Szabo
On Thu, 23 Oct 2003, Christopher Travers wrote: > Hi all; > > I have two tables which have different security considerations wrapped into > a view. Inserting into the view is done using a simple rule which inserts > into both tables (tables have a 1:1 relationship and reflect the > user-defined

[BUGS] BUG: PLPGSQL function causes PgSQL process to die when inserting into a view

2003-10-23 Thread Christopher Travers
Hi all; I have two tables which have different security considerations wrapped into a view. Inserting into the view is done using a simple rule which inserts into both tables (tables have a 1:1 relationship and reflect the user-defined and admin-defined portions of a user profile). From psql,