Re: pg_dump save command in output

From: Daniel Gustafsson <daniel(at)yesql(dot)se>
To: Joao Miguel Ferreira <joao(dot)miguel(dot)c(dot)ferreira(at)gmail(dot)com>
Cc: pgsql-general <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: pg_dump save command in output
Date: 2021-10-06 09:33:30
Message-ID: 64E0A4EF-46C8-4973-A8EF-2F13BCA13C73@yesql.se
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

> On 3 Oct 2021, at 18:56, Joao Miguel Ferreira <joao(dot)miguel(dot)c(dot)ferreira(at)gmail(dot)com> wrote:

> is there a way to ask pg_dump to save a comment in the output file with the full command it is executing ?

I think this idea has some merit. Given the amount of switches for tailoring
the dump that pg_dump has there is a point to knowing just which ones were
used. Connection level parameters should probably be scrubbed, but
object-level filtering etc could be handy.

Would you like to try and propose a patch for pg_dump to implement this?

--
Daniel Gustafsson https://vmware.com/

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Joao Miguel Ferreira 2021-10-06 09:44:43 Re: pg_dump save command in output
Previous Message Pavel Stehule 2021-10-06 06:42:57 Re: type bug?