Postgres Pro
Downloads
Home   >   mailing lists

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

From Gerdan Rezende dos Santos
Subject Re: [PATCH] add option to pg_dumpall to exclude tables from the dump
Date
Msg-id CAKOcMA6yi6P1ZLLqi1=VC3d4Xo9FiiZOMuRe1-ieUPgQ2X-n_w@mail.gmail.com
Whole thread Raw
In response to Re: [PATCH] add option to pg_dumpall to exclude tables from the dump  (Jim Nasby <Jim.Nasby@BlueTreble.com>)
Responses Re: [PATCH] add option to pg_dumpall to exclude tables from the dump  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
Tree view
On Fri, Aug 19, 2016 at 12:38 PM, Jim Nasby <Jim.Nasby@bluetreble.com> wrote:
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


--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers


After review, I realized that there is a call to the function: doShellQuoting (pgdumpopts, OPTARG), which no longer seems to exist ...
After understand the code, I saw that the call is appendShellString (pgdumpopts, OPTARG).

Follow the patches already with the necessary corrections.

Regards
Gerdan Rezende dos Santos
PostgreSQL & EnterpriseDB Specialist, Support, Training & Services
+55 (61) 9645-1525

Attachment

pgsql-hackers by date:

Previous
From: Peter Geoghegan
Date:
Subject: Re: ICU integration
Next
From: Peter Geoghegan
Date:
Subject: Re: ICU integration