pg_dump - Mailing list pgsql-hackers

From wieck@debis.com (Jan Wieck)
Subject pg_dump
Date
Msg-id m1258bN-0003kGC@orion.SAPserv.Hamburg.dsh.de
Whole thread Raw
List 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@debis.com (Jan Wieck) #

pgsql-hackers by date:

Previous
From: wieck@debis.com (Jan Wieck)
Date:
Subject: scanner/parser for FOREIGN KEY
Next
From: Tom Lane
Date:
Subject: Re: [HACKERS] scanner/parser for FOREIGN KEY