From: | Richard Huxton <dev(at)archonet(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | 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 11:21:27 |
Message-ID: | 45263C37.6000209@archonet.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane wrote:
> Kris Jurka <books(at)ejurka(dot)com> writes:
>> Testing out the new pg_dump exclusion switches I've found that excluding a
>> table means that no functions or types will be dumped. Excluding one
>> table shouldn't exclude these objects.
>
> I tend to agree ... will see if I can make it happen. (I never did get
> around to reviewing that patch, anyway ...)
>
> One issue is what to do with procedural languages and large objects,
> which don't have any associated schema. If we treat them as being
> outside all schemas, we'd have semantics like this: dump the PLs and
> blobs unless one or more --schema switches appeared. Is that OK?
Is there a reason why pg_dump can't do the --list/--use-list flags like
pg_restore, or is it just a matter of round tuits?
--
Richard Huxton
Archonet Ltd
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2006-10-06 12:40:53 | Re: pg_dump exclusion switches and functions/types |
Previous Message | Magnus Hagander | 2006-10-06 09:59:52 | Re: Win XP SP2 SMP locking (8.1.4) |