Re: [PATCH] add option to pg_dumpall to exclude tables from the dump - Mailing list pgsql-hackers

From Jim Nasby
Subject Re: [PATCH] add option to pg_dumpall to exclude tables from the dump
Date
Msg-id dc45d41a-12cf-cce0-8cff-9d5c32280a1c@BlueTreble.com
Whole thread Raw
In response to Re: [PATCH] add option to pg_dumpall to exclude tables from the dump  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [PATCH] add option to pg_dumpall to exclude tables from the dump  (Gerdan Rezende dos Santos <gerdan@gmail.com>)
List pgsql-hackers
On 8/18/16 5:01 PM, Tom Lane wrote:
>> I agree, but I think mandating a database name (which I suppose could be
>> > *) with the specifiers would solve that issue.
> Hmm, something like "-T dbname1:pattern1 -T dbname2:pattern2" ?

Bingo. Hopefully there'd be some way to consolidate the code between the 
two as well...
-- 
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com
855-TREBLE2 (855-873-2532)   mobile: 512-569-9461



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: Re: PROPOSAL: make PostgreSQL sanitizers-friendly (and prevent information disclosure)
Next
From: Jim Nasby
Date:
Subject: Re: anyelement -> anyrange