| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Jan Wieck <JanWieck(at)yahoo(dot)com> |
| Cc: | Philip Warner <pjw(at)rhyme(dot)com(dot)au>, Joel Burton <jburton(at)scw(dot)org>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Re: [BUG?] tgconstrrelid doesn't survive a dump/restore |
| Date: | 2001-04-19 14:40:28 |
| Message-ID: | 20650.987691228@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Jan Wieck <JanWieck(at)yahoo(dot)com> writes:
> IMHO there's nothing fundamentally wrong with having pg_dump
> dumping the constraints as special triggers, because they are
> implemented in PostgreSQL as triggers. ...
> The advantage of having pg_dump output these constraints as
> proper ALTER TABLE commands would only be readability and
> easier portability (from PG to another RDBMS).
More to the point, it would allow easier porting to future Postgres
releases that might implement constraints differently. So I agree with
Philip that it's important to have these constructs dumped symbolically
wherever possible.
However, if that's not likely to happen right away, I think a quick hack
to restore tgconstrrelid in the context of the existing approach would
be a good idea.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Lockhart | 2001-04-19 14:54:20 | Re: get difference between two timestamp value in second? |
| Previous Message | Philip Warner | 2001-04-19 14:32:21 | Re: Re: [BUG?] tgconstrrelid doesn't survive a dump/restore |