| From: | Martín Marqués <martin(at)2ndquadrant(dot)com> |
|---|---|
| To: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Minor documentation patch |
| Date: | 2016-05-11 11:00:21 |
| Message-ID: | 304ec41b-baa4-f71a-0b4f-df054c71760e@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
Yesterday I was going over some consultancy and went to check some
syntax for CREATE FUNCTION, particularly related to SECURITY DEFINER part.
Reading there I saw a paragraph which had a sentence that wasn't very
clear at first.
The patch's description gives a better idea on the change, and how I got
there, and I believe it gives better meaning to the sentence in question.
I applied the same change on another part which had the same phrase.
Cheers,
--
Martín Marqués http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| Attachment | Content-Type | Size |
|---|---|---|
| 0001-While-reading-the-CREATE-FUNCTION-reference-docs-for.patch | text/x-patch | 2.3 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2016-05-11 13:40:09 | Re: ALTER TABLE lock downgrades have broken pg_upgrade |
| Previous Message | Ashutosh Bapat | 2016-05-11 09:03:49 | Re: Use %u to print user mapping's umid and userid |