| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Bryn Llewellyn <bryn(at)yugabyte(dot)com>, Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, pgsql-general list <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: alter function/procedure depends on extension |
| Date: | 2022-04-12 15:55:24 |
| Message-ID: | CAKFQuwb_QtY25feLeh=8uNdnyo1H=cN4R3vENsUwQzJP4-0xZg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Tue, Apr 12, 2022 at 8:49 AM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> "David G. Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> writes:
> > - A function that's marked as dependent on an extension is
> automatically
> > - dropped when the extension is dropped.
> > + A function that's marked as dependent on an extension is skipped
> during
> > + dependency checking in restrict mode <xref
> linkend="sql-dropextension"/>.
>
> That is absolutely not an improvement. The proposed replacement text
> is about as clear as mud.
>
+ A function that's marked as dependent on an extension is dropped when the
extension is dropped, even if cascade is not specified.
I suppose that is a wordier way to say "automatically" but referencing the
actual command keyword seems beneficial.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jerry Sievers | 2022-04-12 23:07:02 | Feedback about hybrid SAN snap and rsync'd approach for large systemcloning |
| Previous Message | Tom Lane | 2022-04-12 15:49:29 | Re: alter function/procedure depends on extension |