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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: 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 19:40:11
Message-ID: 21499.1471549211@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Juergen Hannappel <juergen(at)juergen-hannappel(dot)de> writes:
> A new option -T --exlude-table for pg_dumpall. This option is then
> passed through to the pg_dump which really does the work.
> This feature can be used to exclude large tables that are known not
> to change from a database backup dump so that only the changing parts
> of the database are dumped.

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.

Also, if we believe that this has a safe use-case, why only -T, and
not pg_dump's other object selectivity options?

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Stefan Kaltenbrunner 2016-08-18 19:41:57 Re: WIP: About CMake v2
Previous Message Alvaro Herrera 2016-08-18 19:39:46 Re: [COMMITTERS] pgsql: Fix deletion of speculatively inserted TOAST on conflict