On 8/18/16 2:40 PM, Tom Lane wrote:
> This seems pretty dubious to me, in particular that the identical -T
> option will be passed willy-nilly into the pg_dump runs for every
> database. That seems more likely to be a foot-gun than something useful.
I agree, but I think mandating a database name (which I suppose could be
*) with the specifiers would solve that issue.
> Also, if we believe that this has a safe use-case, why only -T, and
> not pg_dump's other object selectivity options?
+1.
--
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