Re: Table constraint ordering disrupted by pg_dump

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: pholben(at)greatbridge(dot)com, pgsql-bugs(at)postgresql(dot)org
Subject: Re: Table constraint ordering disrupted by pg_dump
Date: 2001-04-02 20:40:24
Message-ID: 22438.986244024@sss.pgh.pa.us
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

pgsql-bugs(at)postgresql(dot)org writes:
> When running a backup/restore version of the regression tests on 7.0.3
> and 7.1RCD1 the following was noted: when the create table command
> contained two constraints, the error messages would reflect that the
> constraints were being checked in a consistent order and error
> messages would show either the constraint name or $1 or $2 if no name
> was used for the constraint which generated the first error. After
> dumping and restoring the database, the order was reversed. As a
> result the meaning of error messages changed.

I don't believe this is a bug. There is no guarantee that constraints
are checked in any particular order.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message pgsql-bugs 2001-04-02 21:45:28 Loosing files after backend crash
Previous Message pgsql-bugs 2001-04-02 20:20:38 Table constraint ordering disrupted by pg_dump