| From: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> |
|---|---|
| To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Open items |
| Date: | 2003-10-29 01:51:27 |
| Message-ID: | 3F9F1D1F.70902@familyhealth.com.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> OK, doesn't look like we are going to add the ability to turn off
> constraint checking for reload, nor add ANALYZE as part of ALTER TABLE
> ADD FOREIGN KEY, so we only have a few items left.
Hey - what about if you just delete the pg_constraint entries for all
your foreign keys, then won't they all be dumped as CREATE CONSTRAINT
TRIGGERs?
Then, after restore, you can just re-run contrib/adddepend?
Chris
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Christopher Kings-Lynne | 2003-10-29 01:53:48 | Re: [HACKERS] Autocomplete <TAB> on Postgres7.4beta5 not working? |
| Previous Message | Sean Chittenden | 2003-10-29 01:13:27 | Re: Call for port reports |