| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | patrick(dot)refondini(at)pobox(dot)com |
| Cc: | pgsql-docs(at)postgresql(dot)org |
| Subject: | Re: SYSID can no longer be specified |
| Date: | 2017-10-03 14:15:20 |
| Message-ID: | 9646.1507040120@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
patrick(dot)refondini(at)pobox(dot)com writes:
> The CREATE USER doc still states SYSID can be specified although I obtained:
> SYSID can no longer be specified
I don't really see a problem here. CREATE USER points you to CREATE ROLE
for everything beyond the synopsis, and CREATE ROLE clearly states
The <literal>SYSID</literal> clause is ignored, but is accepted
for backwards compatibility.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David G. Johnston | 2017-10-03 14:25:43 | Re: Doc BUG and/or Change Request: Include Postgres's system columns in reserved words in docs, Chnage to previx sytem colums with 2 underscores? |
| Previous Message | Euler Taveira | 2017-10-03 13:13:23 | Re: Doc BUG and/or Change Request: Include Postgres's system columns in reserved words in docs, Chnage to previx sytem colums with 2 underscores? |