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: pgsql-patches(at)postgresql(dot)org
Subject: Re: Feature: give pg_dump a WHERE clause expression
Date: 2008-06-01 19:47:16
Message-ID: 25899.1212349636@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:
> So, if this patch is not acceptable as-is, what would you feel about
> this:
> I could enhance the -t/--table=NAME option to accept more than a
> simple NAME. Rather it could accept something in the form:

> --table=<table_name>:<where-clause expression>

Well, that would at least address the complaint that it doesn't scale
to multiple tables, but the whole thing still seems like a frammish
that will never see enough use to justify maintaining it.

(BTW, what will you do with a table whose name contains a colon?)

regards, tom lane

In response to

Responses

Browse pgsql-patches by date

  From Date Subject
Next Message Andrew Dunstan 2008-06-01 20:13:34 Re: Feature: give pg_dump a WHERE clause expression
Previous Message Tom Lane 2008-06-01 19:37:20 Re: [BUGS] BUG #4203: perform dblink() in begin/exception returns wrong SQLSTATE code