Re: db partial dumping with pg_dump - Mailing list pgsql-hackers

From Tom Lane
Subject Re: db partial dumping with pg_dump
Date
Msg-id 29054.1029267743@sss.pgh.pa.us
Whole thread Raw
In response to Re: db partial dumping with pg_dump  (Bruce Momjian <pgman@candle.pha.pa.us>)
List pgsql-hackers
Bruce Momjian <pgman@candle.pha.pa.us> writes:
> Clearly, we should shoot for something that leverages the existing
> SELECT code rather than hang more clauses off of COPY.

Yeah, that's a good point.  COPY IN is still a special case, I think,
but seems like COPY OUT could be reimplemented as a special tuple
destination for the regular executor machinery.

Q: how much performance hit would we be taking?  If this slows down
pg_dump a lot, the extra code is worth keeping.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Everything is now "required by the database system"
Next
From: Peter Eisentraut
Date:
Subject: Re: regression test failure