| From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> | 
|---|---|
| To: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> | 
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> | 
| Subject: | Re: DROP FUNCTION of multiple functions | 
| Date: | 2017-02-27 06:46:29 | 
| Message-ID: | CAB7nPqRZPyBD=X64kipRVoMArm=f8RZQwTeVCyt8tuVtB-taxg@mail.gmail.com | 
| Views: | Whole Thread | Raw Message | Download mbox | Resend email | 
| Thread: | |
| Lists: | pgsql-hackers | 
On Sat, Feb 25, 2017 at 10:27 PM, Peter Eisentraut
<peter(dot)eisentraut(at)2ndquadrant(dot)com> wrote:
> Here is a new patch set that addresses your comments.  The structure is
> still the same, just a bunch of things have been renamed based on
> suggestions.
+  <para>
+   Drop multiple functions in one command:
+<programlisting>
+DROP FUNCTION sqrt(integer), sqrt(bigint);
+</programlisting></para>
  </refsect1>
Perhaps adding as well on the page of DROP OPERATOR an example
dropping multiple operators at once?
-DropPolicyStmt:
-           DROP POLICY name ON any_name opt_drop_behavior
-               {
Oh, nice. I can see that you have decided to bit the bullet. Thanks
for considering that.
I am marking this patch as ready for committer, aka you.
-- 
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2017-02-27 06:51:38 | Re: Enabling parallelism for queries coming from SQL or other PL functions | 
| Previous Message | Robert Haas | 2017-02-27 06:46:17 | Re: Creation of "Future" commit fest, named 2017-07 |