| From: | John Naylor <john(dot)naylor(at)enterprisedb(dot)com> |
|---|---|
| To: | Xiong He <iihero(at)qq(dot)com> |
| Cc: | Daniel Gustafsson <daniel(at)yesql(dot)se>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, pgsql-bugs <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: About the function current_user |
| Date: | 2023-03-20 12:13:48 |
| Message-ID: | CAFBsxsFOXZtvw6DZcVQSftc6WF35ZzrmqWPx23r+XHM88pYqmQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Mon, Mar 20, 2023 at 4:35 PM Xiong He <iihero(at)qq(dot)com> wrote:
>
> Great. So if it's in the PG_KEYWORD list, we should not use current_*()?
That was just an explanation, regarding "reserved keywords", since you
asked "why".
The documentation should have the correct uses. If it does, there is no bug
here.
Speaking of bugs, I was wondering why appendix C didn't show up when
searching within the doc website -- it's because the heading in appendix C
spells it "key words", a spelling which seems non-standard and gets
interpreted as "keywords" in a web search.
--
John Naylor
EDB: http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | John Naylor | 2023-03-20 12:16:58 | Re: About the function current_user |
| Previous Message | Uytterhoeven Patrik | 2023-03-20 10:51:13 | Postgres common repo is missing geos310-3.10.3-1.rhel8.x86_64 |