Re: Pre-v11 appearances of the word "procedure" in v11 docs

From: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
To: Peter Geoghegan <pg(at)bowt(dot)ie>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Pre-v11 appearances of the word "procedure" in v11 docs
Date: 2018-08-17 14:15:00
Message-ID: 733b81b5-6f22-22a2-9253-df1e84ad670c@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Attached are my proposed patches. The first is the documentation
change, which basically just substitutes the words, with some occasional
rephrasing. And then patches to extend the syntaxes of CREATE OPERATOR,
CREATE TRIGGER, and CREATE EVENT TRIGGER to accept FUNCTION in place of
PROCEDURE. I decided to do that because with the adjustments from the
first patch, the documentation had become comically inconsistent in some
places and it was easier to just fix the underlying problem than to
explain the reasons for the inconsistencies everywhere. I didn't go
around change all the commands in contrib modules etc. to keep the patch
size under control. This could perhaps be done later.

--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

Attachment Content-Type Size
0001-doc-Update-uses-of-the-word-procedure.patch text/plain 63.2 KB
0002-Change-PROCEDURE-to-FUNCTION-in-CREATE-OPERATOR-synt.patch text/plain 9.3 KB
0003-Change-PROCEDURE-to-FUNCTION-in-CREATE-TRIGGER-synta.patch text/plain 18.7 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2018-08-17 14:27:19 Re: Memory leak with CALL to Procedure with COMMIT.
Previous Message Tom Lane 2018-08-17 13:53:48 Re: Fix help option of contrib/oid2name