| From: | wieck(at)debis(dot)com (Jan Wieck) |
|---|---|
| To: | pgsql-hackers(at)postgreSQL(dot)org (PostgreSQL HACKERS) |
| Subject: | pg_dump |
| Date: | 100-01-03 14:36:53 |
| Message-ID: | m1258bN-0003kGC@orion.SAPserv.Hamburg.dsh.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
is there someone already working on adding all the
requirements for the proposed new features to pg_dump? I
think about the referential integrity triggers etc.
AFAIK, the definition of FOREIGN KEY will make data only
dumps not to work any more. Don't know if a full dump will
work either.
The dump must disable (remove/recreate) ALL triggers on the
tables during data reload.
With less than 1 month left 'til BETA, I think it's time to
start on it.
Jan
--
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me. #
#========================================= wieck(at)debis(dot)com (Jan Wieck) #
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jan Wieck | 0100-01-03 15:22:21 | Re: [HACKERS] scanner/parser for FOREIGN KEY |
| Previous Message | Jan Wieck | 0100-01-03 13:24:05 | scanner/parser for FOREIGN KEY |