Re: Feature: give pg_dump a WHERE clause expression

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Davy Durham <pubaddr5(at)davyandbeth(dot)com>
Cc: Stephen Frost <sfrost(at)snowman(dot)net>, pgsql-patches(at)postgresql(dot)org
Subject: Re: Feature: give pg_dump a WHERE clause expression
Date: 2008-06-02 02:47:34
Message-ID: 1077.1212374854@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-patches

Davy Durham <pubaddr5(at)davyandbeth(dot)com> writes:
> To reiterate, it is not possible to use the COPY command to create
> standard SQL INSERT statements that can be conveniently loaded by
> another db. No?

Fair point, but the question here is about how useful this incremental
feature really is compared to its incremental maintenance cost.
It is *possible* to achieve what you want without any pg_dump
changes: create a fresh table via
CREATE TABLE tmp_table AS SELECT * FROM my_table WHERE ...
and then pg_dump that. So the issue is how often does this problem
come up and is it worth maintaining more code to make it a bit
easier to deal with? My thought is probably not, and that seems
to be the majority opinion so far.

regards, tom lane

In response to

Browse pgsql-patches by date

  From Date Subject
Next Message Davy Durham 2008-06-02 04:10:29 Re: Feature: give pg_dump a WHERE clause expression
Previous Message Stephen Frost 2008-06-02 02:19:37 Re: Feature: give pg_dump a WHERE clause expression