Re: proposal: possibility to read dumped table's name from file

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: proposal: possibility to read dumped table's name from file
Дата
Msg-id 3183720.1626131795@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Re: proposal: possibility to read dumped table's name from file  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Ответы Re: proposal: possibility to read dumped table's name from file
Re: proposal: possibility to read dumped table's name from file
Список pgsql-hackers
Alvaro Herrera <alvherre@2ndquadrant.com> writes:
> [1] your proposal of "[+-] OBJTYPE OBJIDENT" plus empty lines allowed
>     plus lines starting with # are comments, seems plenty.  Any line not
>     following that format would cause an error to be thrown.

I'd like to see some kind of keyword on each line, so that we could extend
the command set by adding new keywords.  As this stands, I fear we'd end
up using random punctuation characters in place of [+-], which seems
pretty horrid from a readability standpoint.

I think that this file format should be designed with an eye to allowing
every, or at least most, pg_dump options to be written in the file rather
than on the command line.  I don't say we have to *implement* that right
now; but if the format spec is incapable of being extended to meet
requests like that one, I think we'll regret it.  This line of thought
suggests that the initial commands ought to match the existing
include/exclude switches, at least approximately.

Hence I suggest

    include table PATTERN
    exclude table PATTERN

which ends up being the above but with words not [+-].

            regards, tom lane



В списке pgsql-hackers по дате отправления:

Предыдущее
От: Ranier Vilela
Дата:
Сообщение: Re: Add proper planner support for ORDER BY / DISTINCT aggregates
Следующее
От: Tom Lane
Дата:
Сообщение: Bogus HAVE_DECL_FOO entries in msvc/Solution.pm