Postgres planner bug in 7.3.x and 7.4.1 ?

From: Laurent Perez <downloader(at)free(dot)fr>
To: pgsql-general(at)postgresql(dot)org
Subject: Postgres planner bug in 7.3.x and 7.4.1 ?
Date: 2004-01-09 10:02:10
Message-ID: 6.0.0.22.2.20040109104428.03eac7a8@pop3.free.fr
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Hello

We're experiencing weird behaviours with both Postgres 7.3.x and 7.4.1
versions, relating to views based on views including fields based upon
plpgsql functions. Attached is a .sql file showing our problems, from a
co-worker who doesn't have immediate access to this mailing list.

Here's the psql output on a 7.4.1 version (t1, t2 already created), showing
the function being called :

postgres(at)msi:/$ psql -p5433 -d t2g_3 -f /tmp/t1.sql
You are now connected as new user postgres.
psql:/tmp/t1.sql:32: ERROR: function "plpgsql_call_handler" already exists
with same argument types
psql:/tmp/t1.sql:35: ERROR: language "plpgsql" already exists
CREATE FUNCTION
CREATE VIEW
CREATE VIEW
CREATE VIEW
CREATE VIEW
psql:/tmp/t1.sql:284: NOTICE: f1 >>>>>>>> 8980
psql:/tmp/t1.sql:284: NOTICE: f1 >>>>>>>> 8981
psql:/tmp/t1.sql:284: NOTICE: f1 >>>>>>>> 8982
num_adr | num_person | firstname | name
---------+------------+-----------+------
6231 | 8982 | Chico | Marx
(1 row)

num_adr | num_person | firstname | name
---------+------------+-----------+------
6231 | 8982 | Chico | Marx
(1 row)

Thanks for any support

laurent

Attachment Content-Type Size
t1.sql application/octet-stream 5.2 KB

Responses

Browse pgsql-general by date

  From Date Subject
Next Message D. Dante Lorenso 2004-01-09 10:11:08 Re: Using indices with long unique IDs.
Previous Message Sergey Olefir 2004-01-09 09:42:04 Using indices with long unique IDs.