Subject: Re: Users/Roles do not align.
To: pgsql-docs@lists.postgresql.org
References: <158057750885.1123.2806779262588618988@wrigleys.postgresql.org>
Cc: jbird@nuna.com
From: =?UTF-8?Q?J=c3=bcrgen_Purtz?= <juergen@purtz.de>
Message-ID: <2a273cf6-51be-a25b-5ef6-915ca727d4db@purtz.de>
Date: Tue, 4 Feb 2020 07:39:50 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101
 Thunderbird/68.4.1
MIME-Version: 1.0
In-Reply-To: <158057750885.1123.2806779262588618988@wrigleys.postgresql.org>
Content-Type: multipart/alternative;
 boundary="------------4C2EDC4270E55FDC13003B9A"
Content-Language: en-US
Precedence: bulk

This is a multi-part message in MIME format.
--------------4C2EDC4270E55FDC13003B9A
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit


> Based on this, I believe Section 5.9 should read:
> `A PostgreSQL database cluster contains one or more named databases. Roles
> are shared across the entire cluster, but no other data is shared across
> databases. Any given client connection to the server can access only the
> data in a single database, the one specified in the connection request.`

imo the following is a more precise wording:

'A cluster contains three or more named databases ('template0', 
'template1', 'postgres', ...). Roles, which are users or groups, see 
Chapter 21, - as well as database names and tablespace definitions - are 
shared across the entire cluster. No other data is shared across 
databases or schemas. Any given client connection to the server can 
access only the data in a single database, the one specified in the 
connection request. If it has the necessary privileges, the connection 
can access all schemas within this database.'

And the last sentence of the paragraph behind 'Note' shall be extended, 
because schemas are rigidly separated from each other - only the access 
to different schemas is easily done from a single connection.

'Unlike _access to_ databases, _access to_ schemas is not rigidly 
separated: a _connection_ can access objects in any of the schemas in 
the database they are connected to, if they have privileges to do so.'


J. Purtz


--------------4C2EDC4270E55FDC13003B9A
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <br>
    <blockquote type="cite"
      cite="mid:158057750885.1123.2806779262588618988@wrigleys.postgresql.org">
      <pre class="moz-quote-pre" wrap="">Based on this, I believe Section 5.9 should read:
`A PostgreSQL database cluster contains one or more named databases. Roles
are shared across the entire cluster, but no other data is shared across
databases. Any given client connection to the server can access only the
data in a single database, the one specified in the connection request.`
</pre>
    </blockquote>
    <p>imo the following is a more precise wording:</p>
    <p>'A cluster contains three or more named databases ('template0',
      'template1', 'postgres', ...). Roles, which are users or groups,
      see Chapter 21, - as well as database names and tablespace
      definitions - are shared across the entire cluster. No other data
      is shared across databases or schemas. Any given client connection
      to the server can access only the data in a single database, the
      one specified in the connection request. If it has the necessary
      privileges, the connection can access all schemas within this
      database.'<br>
    </p>
    <p>And the last sentence of the paragraph behind 'Note' shall be
      extended, because schemas are rigidly separated from each other -
      only the access to different schemas is easily done from a single
      connection.<br>
    </p>
    <p>'Unlike <u>access to</u> databases, <u>access to</u> schemas is
      not rigidly separated: a <u>connection</u> can access objects in
      any of the schemas in the database they are connected to, if they
      have privileges to do so.'<br>
    </p>
    <p><br>
    </p>
    <p>J. Purtz<br>
    </p>
  </body>
</html>

--------------4C2EDC4270E55FDC13003B9A--