From: | Mike Mascari <mascarm(at)mascari(dot)com> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Is pg_dump still broken? |
Date: | 2000-01-18 00:17:05 |
Message-ID: | 3883B101.E0593FE7@mascari.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Sunday, I downloaded the newest snapshot of pg_dump, with Tom's fixes
applied (it no longer dumps core when dumping indexes). However, pg_dump
is incorrectly dumping argument lists for trigger procedures:
test=# drop trigger mytrigger on mytable;
DROP
test=# create trigger mytrigger
before insert on mytable
for each row execute procedure autoinc ('myfield', 'myseq');
CREATE
[postgres(at)ferrari /tmp]$ pg_dump test
...
CREATE TRIGGER "mytrigger" BEFORE INSERT ON "mytable" FOR EACH ROW
EXECUTE PROCEDURE autoinc ('myfield', 'myfieldmyseq');
...
Note the second parameter to autoinc() -- it should be 'myseq', not
'myfieldmyseq'. I suspect someone isn't doing a resetPQExpBuffer()
somewhere. Can anyone confirm this?
Mike Mascari
From | Date | Subject | |
---|---|---|---|
Next Message | Hannu Krosing | 2000-01-18 00:19:17 | Re: [HACKERS] Foreign keys: unexpected result from ALTER TABLE... ADD CONSTRAINT... |
Previous Message | The Hermit Hacker | 2000-01-18 00:08:14 | Re: [HACKERS] bugs@postgresql.org? |