| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: PG 13 release notes, first draft |
| Date: | 2020-05-05 15:22:25 |
| Message-ID: | 20200505152225.GA13016@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
In this item
+<listitem>
+<!--
+Author: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
+2020-04-20 [5fc703946] Add ALTER .. NO DEPENDS ON
+-->
+
+<para>
+Add the ability to remove a function's dependency on an extension (Alvaro Herrera)
+</para>
+
+<para>
+The syntax is ALTER FUNCTION .. NO DEPENDS ON.
+</para>
+
+</listitem>
This works for several object types, not just a functions. I propose
Add the ability to remove an object's dependency on an extension (Álvaro Herrera)
The object can be a function, materialized view, index, or trigger.
The syntax is ALTER .. NO DEPENDS ON.
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2020-05-05 15:23:50 | Re: PG 13 release notes, first draft |
| Previous Message | Tom Lane | 2020-05-05 15:17:24 | Re: Poll: are people okay with function/operator table redesign? |