From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Vik Fearing <vik(at)postgresfriends(dot)org> |
Cc: | Lætitia Avrot <laetitia(dot)avrot(at)gmail(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: pg_dump new feature: exporting functions only. Bad or good idea ? |
Date: | 2021-03-17 17:16:23 |
Message-ID: | 3523389.1616001383@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Vik Fearing <vik(at)postgresfriends(dot)org> writes:
> On 3/17/21 6:00 PM, Lætitia Avrot wrote:
>> However, when I finally got the time to look at it in detail, I found out
>> there was no way to solve the dependencies in the functions and procedures,
>> so that the exported file, when re-played could lead to invalid objects.
>> ...
>> So, my question is: what do you think about such a feature? is it worth it?
> Yes, it is absolutely worth it to be able to extract just the functions
> from a database. I have wanted this several times.
Selective dumps always have a risk of not being restorable on their
own; I don't see that "functions only" is noticeably less safe than
"just these tables", or other cases that we support already.
What I'm wondering about is how this might interact with the
discussion at [1].
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tomas Vondra | 2021-03-17 17:25:58 | Re: PoC/WIP: Extended statistics on expressions |
Previous Message | Fabrízio de Royes Mello | 2021-03-17 17:15:52 | Re: pg_dump new feature: exporting functions only. Bad or good idea ? |