Re: [PATCH] add option to pg_dumpall to exclude tables from the dump

From: Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Juergen Hannappel <juergen(at)juergen-hannappel(dot)de>
Cc: <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [PATCH] add option to pg_dumpall to exclude tables from the dump
Date: 2016-08-18 21:29:54
Message-ID: c5465a13-85f4-6fbb-29b3-2e072d1523d9@BlueTreble.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Claudio Freire 2016-08-18 21:31:39 Re: [WIP] [B-Tree] Keep indexes sorted by heap physical location
Previous Message Tom Lane 2016-08-18 21:27:45 Re: [WIP] [B-Tree] Keep indexes sorted by heap physical location