Re: pg_dump: Sorted output, referential integrity
От | Philip Warner |
---|---|
Тема | Re: pg_dump: Sorted output, referential integrity |
Дата | |
Msg-id | 3.0.5.32.20011211133601.03b4b7c0@mail.rhyme.com.au обсуждение исходный текст |
Ответ на | Re: pg_dump: Sorted output, referential integrity (Stephan Szabo <sszabo@megazone23.bigpanda.com>) |
Ответы |
Re: pg_dump: Sorted output, referential integrity
|
Список | pgsql-hackers |
At 13:34 7/12/01 -0800, Stephan Szabo wrote: > >Well, the biggest thing I see on using alter table add constraint for >foreign keys is the expense involved if you do it after the tables are >populated. Is it really worse than loading the tables with the constraint in place? >I chose the theoretical cleanliness of checking each row >using the code we had over the speed of doing a special check for the >alter table case, Out of curiosity - what was the difference? By the sounds of it, we may get 'alter table' in pg_dump by 7.3 or 7.4. ---------------------------------------------------------------- Philip Warner | __---_____ Albatross Consulting Pty. Ltd. |----/ - \ (A.B.N. 75 008 659 498) | /(@) ______---_ Tel: (+61) 0500 83 82 81 | _________ \ Fax: (+61) 0500 83 82 82 | ___________ | Http://www.rhyme.com.au | / \| | --________-- PGP key available upon request, | / and from pgp5.ai.mit.edu:11371 |/
В списке pgsql-hackers по дате отправления: