[BUGS] Bug #839: triggers do not execute in right order in procedures

2002-12-05 Thread pgsql-bugs
Eugene Gridasov ([EMAIL PROTECTED]) reports a bug with a severity of 1 The lower the number the more severe it is. Short Description triggers do not execute in right order in procedures Long Description The constraint trigger on delete executes ONLY after procedure completion, but it does not exe

Re: [BUGS] Bug #837: Unable to use LATIN9 (=ISO-8859-15) encoding

2002-12-05 Thread Peter Eisentraut
> >From PSQL, if I perform: > \encoding LATIN9 > insert into i18ntest(id, data) values('Euro symbol', '¤'); > > then I would expect this to insert a euro symbol into the data column '¤' means '¤', not anything else. Maybe you want to try '\244' (octal). -- Peter Eisentraut [EMAIL PROTECTED]

bogus varno EXPLAIN bug (was Re: [BUGS] Explain analyze gives bogusvarno for dblink views)

2002-12-05 Thread Joe Conway
Kris Jurka wrote: This behavior is present in 7.3 as well. On Thu, 5 Dec 2002, Kris Jurka wrote: Using the old < 7.3 version of dblink on 7.4devel gives a "get_names_for_var: bogus varno 5" error. I can confirm this both on cvs tip (pulled after noon PST today) and 7.3 stable branch. It is no

[BUGS] Bug #838: SSL problems in 7.3

2002-12-05 Thread pgsql-bugs
Nathan Mueller ([EMAIL PROTECTED]) reports a bug with a severity of 1 The lower the number the more severe it is. Short Description SSL problems in 7.3 Long Description In 7.3 if a client exists without disconnecting from the database the backend dumps core. This wouldn't be so bad except that

Re: [BUGS] Cannot create view with subquery and join clause

2002-12-05 Thread Tom Lane
Robert Osowiecki <[EMAIL PROTECTED]> writes: > /** this one fails with >ERROR: find_expr_references_walker: bogus varno 3 I believe I fixed this yesterday --- see pgsql-general for the patch. regards, tom lane ---(end of broadcast)

[BUGS] Bug #837: Unable to use LATIN9 (=ISO-8859-15) encoding

2002-12-05 Thread pgsql-bugs
Steve Haslam ([EMAIL PROTECTED]) reports a bug with a severity of 2 The lower the number the more severe it is. Short Description Unable to use LATIN9 (=ISO-8859-15) encoding Long Description I am trying to use LATIN9 (ISO-8859-15) as my client encoding rather than LATIN1-- the database I am usi

[BUGS] Cannot create view with subquery and join clause

2002-12-05 Thread Robert Osowiecki
POSTGRESQL BUG REPORT TEMPLATE Your name : Robert Osowiecki Your email address : [EMAIL PROTECTED] System Configurat

Re: [BUGS] Explain analyze gives bogus varno for dblink views

2002-12-05 Thread Kris Jurka
This behavior is present in 7.3 as well. On Thu, 5 Dec 2002, Kris Jurka wrote: > Using the old < 7.3 version of dblink on 7.4devel gives a > "get_names_for_var: bogus varno 5" error. > > Install the deprecated version of dblink by following the directions in > the dblink.sql file to comment / un

[BUGS] Explain analyze gives bogus varno for dblink views

2002-12-05 Thread Kris Jurka
Using the old < 7.3 version of dblink on 7.4devel gives a "get_names_for_var: bogus varno 5" error. Install the deprecated version of dblink by following the directions in the dblink.sql file to comment / uncomment various parts of the script. DROP TABLE t1; CREATE TABLE t1 (a int); DROP TABLE t

[BUGS] GEQO Triggers Server Crash

2002-12-05 Thread Kris Jurka
The following script crashes 7.4devel. SET geqo_threshold=2; CREATE TABLE t1 (a int primary key); CREATE TABLE t2 (a int); SELECT * FROM t1,t2 WHERE t1.a=t2.a; #0 0x0811001c in best_inner_indexscan (root=, rel=, outer_relids=, jointype=) at indxpath.c:1421 1421if (samese