Bug with dump/restore when using UNION and ORDER BY in views

From: "Kristian Eide" <kreide(at)online(dot)no>
To: <pgsql-sql(at)postgresql(dot)org>
Subject: Bug with dump/restore when using UNION and ORDER BY in views
Date: 2002-08-03 21:11:40
Message-ID: 036501c23b32$5c5149f0$6b97f181@speed
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-sql

There seems to be a bug when dumping a view which is a UNION of selects, one
of which has an ORDER BY. A pair of paranthesises around the select is
missing, and this cause a subsequent restore to fail. This is quite annoying
as the backup file must be manually edited before it can be restored, and I
would really appreciate a solution in a future version of Postgre.

This problem is still present in 7.2.1.

Example:

CREATE TABLE t (id INT);
CREATE VIEW v AS (SELECT id FROM t AS t1 ORDER BY id) UNION SELECT id FROM t
AS t2;

After a dump it looks like this:

CREATE VIEW "v" as SELECT t1.id FROM t t1 ORDER BY t1.id UNION SELECT t2.id
FROM t t2;

Which is not accepted by postgre.

Regards,

Kristian

Responses

Browse pgsql-sql by date

  From Date Subject
Next Message Ken Corey 2002-08-03 22:14:43 Re: VACUUM not doing its job?
Previous Message Kristian Eide 2002-08-03 20:53:08 VACUUM not doing its job?