Re: Predictable order of SQL commands in pg_dump

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: dmitry(at)koterov(dot)ru
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Predictable order of SQL commands in pg_dump
Date: 2008-09-21 19:57:22
Message-ID: 8211.1222027042@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

"Dmitry Koterov" <dmitry(at)koterov(dot)ru> writes:
> CREATE TRIGGER t000_set_id
> - BEFORE INSERT OR DELETE OR UPDATE ON a
> + BEFORE INSERT OR DELETE OR UPDATE ON b
> FOR EACH ROW
> EXECUTE PROCEDURE i_trg();

> CREATE TRIGGER t000_set_id
> - BEFORE INSERT OR DELETE OR UPDATE ON b
> + BEFORE INSERT OR DELETE OR UPDATE ON a
> FOR EACH ROW
> EXECUTE PROCEDURE i_trg();

> You see, object names are the same, but ordering is mixed.

Yeah, because the sort is just on object name.

For objects of the same type I suppose we could take a look at their
owning object's name too ...

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Hans-Jürgen Schönig 2008-09-21 20:02:43 Re: Toasted table not deleted when no out of line columns left
Previous Message Andrew Dunstan 2008-09-21 19:28:54 parallel pg_restore