Re: pg_dump exclusion switches and functions/types - Mailing list pgsql-hackers

From Tom Lane
Subject Re: pg_dump exclusion switches and functions/types
Date
Msg-id 2038.1160156213@sss.pgh.pa.us
Whole thread Raw
In response to Re: pg_dump exclusion switches and functions/types  (Andrew Dunstan <andrew@dunslane.net>)
Responses Re: pg_dump exclusion switches and functions/types  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Andrew Dunstan <andrew@dunslane.net> writes:
> Tom Lane wrote:
>> ... Or we could
>> import the rather ad-hoc shell-wildcard-like rules used by psql's \d
>> stuff.  None of these are especially attractive :-(

> 1. regexes, please.

One argument that occurs to me for importing the psql code is that it's
solved the problem of including a schema name in the pattern.  It would
be a lot nicer to say "-t schema.table" than to have to say "-t table -n
schema".  In particular this allows one to dump s1.foo and s2.bar
without also getting s1.bar and s2.foo; a problem that is insoluble if
we have only independent schema and table filters.  I think that ideally
one would only use the schema switches if one actually wanted a
schema-by-schema dump, not as a wart on the side of the
specific-object-selection switches.

The psql code does allow you to get at most of the functionality of
regexes...
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: pg_dump exclusion switches and functions/types
Next
From: Bruce Momjian
Date:
Subject: Backbranch releases