Just a quick question regarding the pg_dump program: I notice that PRIMARY KEY constraints are currently dumped as: PRIMARY KEY ("field") Whereas (to be in line with all the other constraints), it should be dumped as: CONSTRAINT "name" PRIMARY KEY ("field") Otherwise, some poor bugger who went to the trouble of giving his primary keys custom names will lose them with a dump/restore??? Also, if they have defined a function or trigger that refers to that primary key by name, won't it fail after a dump/restore? (If the name has changed?) I'm just asking, because I'm still trying to find something small and self-contained I can work on! Chris
- Re: [HACKERS] pg_dump / Unique constraints Philip Warner
- RE: [HACKERS] pg_dump / Unique constraints Christopher Kings-Lynne
- RE: [HACKERS] pg_dump / Unique constraint... Philip Warner
- Re: [HACKERS] pg_dump / Unique constr... Bruce Momjian
- Re: [HACKERS] pg_dump / Unique co... Tom Lane
- Re: [HACKERS] pg_dump / Uniq... Tom Lane
- Re: [HACKERS] pg_dump / ... Bruce Momjian
- Re: [HACKERS] pg_dump / ... Tom Lane
- Re: [HACKERS] pg_dump / ... Bruce Momjian
- Re: [HACKERS] pg_dump / ... Philip Warner
- [HACKERS] ALTER TABLE...... Christopher Kings-Lynne
- [HACKERS] ALTER TABLE...... Philip Warner
- [HACKERS] RE: ALTER TABL... Christopher Kings-Lynne
- Re: [HACKERS] RE: ALTER ... Tom Lane