Hi all,
I have noticed that psql documentation mentions "system roles", however
in all other parts of the docs, we use the term "default roles".
Shouldn't we make this term more consistent and also add a link to the
table describing those roles? Please see the attached.
Thanks,
--
Michael
diff -
This inconsistency is part of the more general problem that we miss a
chapter, where our basic terms like 'database', 'cluster', 'segment',
'catalog', 'schema', ... are explicitly defined.
Kind regards
Jürgen Purtz
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/9.4/static/continuous-archiving.html
Description:
Most examples in "25.3. Continuous Archiving and Point-in-Time Recovery
(PITR)" use Unix commands and paths, but all variables are written as
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/10/static/app-pg-ctl.html
Description:
ref/pg_ctl-ref.sgml
337,338c337,339
< The options should usually be surrounded by single
or
< double quotes to ensure that they are pass
Hi,
> On Aug 23, 2018, at 5:54 AM, PG Doc comments form
> wrote:
>
> The following documentation comment has been logged on the website:
>
> Page: https://www.postgresql.org/docs/9.4/static/continuous-archiving.html
> Description:
>
> Most examples in "25.3. Continuous Archiving and Point-in-
> On Aug 23, 2018, at 3:58 AM, Michael Paquier wrote:
>
> Hi all,
>
> I have noticed that psql documentation mentions "system roles", however
> in all other parts of the docs, we use the term "default roles".
> Shouldn't we make this term more consistent and also add a link to the
> table descr
On Thu, Aug 23, 2018 at 10:53:35AM +0200, Jürgen Purtz wrote:
> This inconsistency is part of the more general problem that we miss a
> chapter, where our basic terms like 'database', 'cluster', 'segment',
> 'catalog', 'schema', ... are explicitly defined.
You may have a point here, not in the way
Hi,
Looking at privileges that a user would need now a days to create a
cluster clone with repmgr we noticed that there's inaccurate information
in the docs regarding the use of replication functions.
I was able to test on 9.6 and 10 that a user with replication privileges
can create and drop a r
