Re: [HACKERS] Patch: Add --no-comments to skip COMMENTs with pg_dump
От | Michael Paquier |
---|---|
Тема | Re: [HACKERS] Patch: Add --no-comments to skip COMMENTs with pg_dump |
Дата | |
Msg-id | CAB7nPqTTh8j--+=8LocS6TJpbvTyCRSKOp=XkXGiAjHZpa34cw@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: [HACKERS] Patch: Add --no-comments to skip COMMENTs with pg_dump (David Fetter <david@fetter.org>) |
Ответы |
Re: [HACKERS] Patch: Add --no-comments to skip COMMENTs with pg_dump
|
Список | pgsql-hackers |
On Tue, Jul 18, 2017 at 3:45 AM, David Fetter <david@fetter.org> wrote: > The one I run into frequently is in a proprietary fork, RDS Postgres. > It'll happily dump out COMMENT ON EXTENSION plpgsq IS ... > which is great as far as it goes, but errors out when you try to > reload it. > > While bending over backwards to support proprietary forks strikes me > as a terrible idea, I'd like to enable pg_dump to produce and consume > ToCs just as pg_restore does with its -l/-L options. This would > provide the finest possible grain. Let's add as well a similar switch to pg_dumpall that gets pushed down to all the created pg_dump commands. If this patch gets integrated as-is this is going to be asked. And tests would be welcome. -- Michael
В списке pgsql-hackers по дате отправления: