| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Neil Conway <neilconway(at)rogers(dot)com> |
| Cc: | pgman(at)candle(dot)pha(dot)pa(dot)us, pgsql-hackers(at)postgreSQL(dot)org |
| Subject: | Re: pg_dump is broken in CVS tip |
| Date: | 2002-04-12 22:51:27 |
| Message-ID: | 11369.1018651887@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Neil Conway <neilconway(at)rogers(dot)com> writes:
> However, when I created a table using the commands above and then
> dumped it again, I got a dump that worked properly:
> ...
> If you can give me a reproduceable test-case, I'll fix the bug.
Sigh ... I should take my own advice about checking that I've described
a problem completely :-(. It looks like you also need a foreign-key
reference to the table. This will generate the problem:
create table t1 (f1 int primary key);
create table t2 (f1 int references t1);
The dump of t1 will now read
CREATE TABLE "t1" (
"f1" integer NOT NULL,
Constraint "t1_pkey" Primary Key ("f1")
);
Sorry for the inadequate report.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2002-04-12 22:59:33 | Re: pg_dump is broken in CVS tip |
| Previous Message | Jan Wieck | 2002-04-12 22:48:51 | Re: numeric/decimal docs bug? |