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

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Juergen Hannappel <juergen(at)juergen-hannappel(dot)de>
Cc: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [PATCH] add option to pg_dumpall to exclude tables from the dump
Date: 2016-07-07 21:56:16
Message-ID: CA+TgmoYjjQhUkoYDiDO9f59OnFiR2kqE+CN5abvLLZrGWMSFCA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Apr 22, 2016 at 6:42 AM, Juergen Hannappel
<juergen(at)juergen-hannappel(dot)de> wrote:
> 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.
>
> Signed-off-by: Juergen Hannappel <juergen(at)juergen-hannappel(dot)de>

This seems like it could be useful. Please add it to the
currently-open CommitFest so it gets reviewed at some point:

https://commitfest.postgresql.org/action/commitfest_view/open

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Thomas Munro 2016-07-07 22:06:43 Re: SELECT DISTINCT never uses an index?
Previous Message Corey Huinker 2016-07-07 21:52:15 \timing interval