Re: pg_dump new feature: exporting functions only. Bad or good idea ? - Mailing list pgsql-hackers

From Laetitia Avrot
Subject Re: pg_dump new feature: exporting functions only. Bad or good idea ?
Date
Msg-id CAB_COdivDdsmVg3j9_bWqhg6M7qfA1RpD8zPPv8rP01+iaQM8Q@mail.gmail.com
Whole thread Raw
In response to Re: pg_dump new feature: exporting functions only. Bad or good idea ?  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Hello Tom,

Le ven. 25 mars 2022 à 00:18, Tom Lane <tgl@sss.pgh.pa.us> a écrit :
Daniel Gustafsson <daniel@yesql.se> writes:
>> On 24 Mar 2022, at 23:38, Greg Stark <stark@mit.edu> wrote:
>> It looks like this discussion has reached a bit of an impasse with Tom
>> being against this approach and Michael and Daniel being for it. It
>> doesn't look like it's going to get committed this commitfest, shall
>> we move it forward or mark it returned with feedback?

> Lætitia mentioned the other day off-list that she was going to try and update
> this patch with the pattern support proposed, so hopefully we will hear from
> her shortly on that.

To clarify: I'm not against having an easy way to dump all-and-only
functions.  What concerns me is having such a feature that's designed
in isolation, without a plan for anything else.  I'd like to create
some sort of road map for future selective-dumping options, and then
we can make sure that this feature fits into the bigger picture.
Otherwise we're going to end up with an accumulation of warts, with
inconsistent naming and syntax, and who knows what other sources of
confusion.

This totally makes sense.

Have a nice day,

Lætitia
 

                        regards, tom lane

pgsql-hackers by date:

Previous
From: Laetitia Avrot
Date:
Subject: Re: pg_dump new feature: exporting functions only. Bad or good idea ?
Next
From: Dagfinn Ilmari Mannsåker
Date:
Subject: Re: Corruption during WAL replay