Re: Another nasty pg_dump problem

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: Another nasty pg_dump problem
Дата
Msg-id 7435.1059744686@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Re: Another nasty pg_dump problem  (Peter Eisentraut <peter_e@gmx.net>)
Список pgsql-hackers
Peter Eisentraut <peter_e@gmx.net> writes:
> This could be fixed, but note that elsewhere we use

>     /*
>      * Always start with REVOKE ALL FROM PUBLIC, so that we don't have to
>      * wire-in knowledge about the default public privileges for different
>      * kinds of objects.
>      */
>     appendPQExpBuffer(firstsql, "REVOKE ALL ON %s %s FROM PUBLIC;\n",
>                       type, name);

> So maybe this isn't such a bad state after all.

Well, if you want to take that position then the test for "{=UC}" ought
to be ripped out, so that we are consistent about it across backend
versions.
        regards, tom lane


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

Предыдущее
От: Peter Eisentraut
Дата:
Сообщение: Re: SQLSTATEs for warnings
Следующее
От: Tom Lane
Дата:
Сообщение: Re: SQLSTATEs for warnings