| From: | Justin Pryzby <pryzby(at)telsasoft(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Tomas Vondra <tomas(dot)vondra(at)enterprisedb(dot)com>, ahsan hadi <ahsan(dot)hadi(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org, Lætitia AVROT <laetitia(dot)avrot(at)gmail(dot)com> |
| Subject: | Re: pg_dump new feature: exporting functions only. Bad or good idea ? |
| Date: | 2021-07-09 23:50:20 |
| Message-ID: | 20210709235020.GD1301@telsasoft.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Jul 09, 2021 at 07:43:02PM -0400, Tom Lane wrote:
> Tomas Vondra <tomas(dot)vondra(at)enterprisedb(dot)com> writes:
> > The main question I have is whether this should include procedures.
>
> I feel a bit uncomfortable about sticking this sort of limited-purpose
> selectivity mechanism into pg_dump. I'd rather see a general filter
> method that can select object(s) of any type. Pavel was doing some
> work towards that awhile ago, though I think he got frustrated about
> the lack of consensus on details.
That's this: https://commitfest.postgresql.org/33/2573/
--
Justin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2021-07-10 02:55:43 | Re: [PoC] Improve dead tuple storage for lazy vacuum |
| Previous Message | Tom Lane | 2021-07-09 23:43:02 | Re: pg_dump new feature: exporting functions only. Bad or good idea ? |