| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Tomas Vondra <tomas(dot)vondra(at)enterprisedb(dot)com> |
| Cc: | 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:43:02 |
| Message-ID: | 2337130.1625874182@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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. Which is a problem, but I don't
think the solution is to accrue more and more independently-designed-
and-implemented features that each solve some subset of the big problem.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Justin Pryzby | 2021-07-09 23:50:20 | Re: pg_dump new feature: exporting functions only. Bad or good idea ? |
| Previous Message | Jacob Champion | 2021-07-09 23:31:48 | Re: [PATCH] Pull general SASL framework out of SCRAM |