From: | "Dmitry Koterov" <dmitry(at)koterov(dot)ru> |
---|---|
To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Predictable order of SQL commands in pg_dump |
Date: | 2008-09-21 20:03:23 |
Message-ID: | d7df81620809211303y1d280deeka262f5b1764c773c@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Great! Would it be implemented in a next version? Seems it would be
very helpful, especially for people who commit database structure to
CVS/SVN once per minute to track changes history (or similar)...
On Sun, Sep 21, 2008 at 11:57 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> "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
>
From | Date | Subject | |
---|---|---|---|
Next Message | Simon Riggs | 2008-09-21 20:11:12 | Re: Foreign key constraint for array-field? |
Previous Message | Hans-Jürgen Schönig | 2008-09-21 20:02:43 | Re: Toasted table not deleted when no out of line columns left |