From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Richard Huxton <dev(at)archonet(dot)com>, Kris Jurka <books(at)ejurka(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: pg_dump exclusion switches and functions/types |
Date: | 2006-10-06 14:47:17 |
Message-ID: | 45266C75.1080501@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:
>
>> However, ISTM that a similar facility for fine grained control could
>> fairly easily be built into pg_dump.
>>
>
> Yeah ... later.
>
> The way I envision it is that the schema-related switches are fine for
> selecting things at the level of whole schemas, and the table-related
> switches are fine for selecting individual tables, and what we lack are
> inclusion/exclusion switches that operate on other kinds of individual
> objects. Somebody can design and implement those later, if the itch
> strikes. What we have to do today is make sure that the interaction of
> schema and table switches is such that an extension in that direction
> will fit in naturally.
>
>
>
totally agree.
cheers
andrew
From | Date | Subject | |
---|---|---|---|
Next Message | Graham Davis | 2006-10-06 15:05:04 | Re: [HACKERS] timestamp subtraction (was Re: formatting intervals |
Previous Message | Tom Lane | 2006-10-06 14:40:03 | Re: PL/pgSQL Todo, better information in errcontext from plpgsql |