Re: Predictable order of SQL commands in pg_dump - Mailing list pgsql-hackers

From Dmitry Koterov
Subject Re: Predictable order of SQL commands in pg_dump
Date
Msg-id d7df81620809211303y1d280deeka262f5b1764c773c@mail.gmail.com
Whole thread Raw
In response to Re: Predictable order of SQL commands in pg_dump  (Tom Lane <tgl@sss.pgh.pa.us>)
List 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@sss.pgh.pa.us> wrote:
> "Dmitry Koterov" <dmitry@koterov.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
>


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Toasted table not deleted when no out of line columns left
Next
From: Joe Conway
Date:
Subject: Re: [patch] fix dblink security hole