Re: Table data exclusion patch for pg_dump

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Vadim Trochinsky <me(at)vadim(dot)ws>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Table data exclusion patch for pg_dump
Date: 2009-05-01 19:42:46
Message-ID: 49FB50B6.4050706@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane wrote:
> Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
>
>> Tom Lane wrote:
>>
>>> Why wouldn't you just use -s ?
>>>
>
>
>> You might want the whole schema and data for most but not all of the
>> tables (e.g. you might leave out a large session table for a web app).
>>
>
> The use-case seems pretty thin to me, and the potential for shooting
> oneself in the foot rather large. We routinely get complaints, for
> example, from people who do partial dumps and then find out they don't
> restore because of foreign key constraints. This looks like mostly
> a larger-gauge version of that.
>
>
>

Well, you can shoot yourself in the foot using pg_restore's --use-list
option too, but that doesn't mean it's not useful. And indeed it could
be used to achieve the OP's ends, except that he would have spent
useless time and space dumping the data for a table he doesn't want.

cheers

andrew

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message David Fetter 2009-05-01 19:42:55 Re: Throw some low-level C scutwork at me
Previous Message Tom Lane 2009-05-01 19:41:42 Re: Throw some low-level C scutwork at me