From: Giovanni Biscuolo <g@xelera.eu>
To: "Gábor Boskovits" <boskovits@gmail.com>
Cc: 38198-done@debbugs.gnu.org
Subject: bug#38198: missing shell for postgresql system user
Date: Thu, 14 Nov 2019 11:02:15 +0100 [thread overview]
Message-ID: <878soiojx4.fsf@roquette.mug.biscuolo.net> (raw)
In-Reply-To: <CAE4v=pjLFcXP3014+xb6w0fA7iVVEKArey83_E=Zdd0zeAjoGA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1162 bytes --]
Hello Gábor,
Gábor Boskovits <boskovits@gmail.com> writes:
[...]
>> To access a database server on localhost for the first time as the user
>> postgres (the superuser) a person should use:
>>
>> --8<---------------cut here---------------start------------->8---
>> sudo su postgres -c 'psql'
>> --8<---------------cut here---------------end--------------->8---
[...]
> I would not mind this change, I think it is ok. However it is easy to
> work around this with su -s.
> I usually do that.
Oh, that's the real solution: thanks! (I should study more...)
sudo su postgres -s psql
Since giving a shell to the postgres user is **not** the solution, I'm
closing this bug.
I'll try to send a patch to the relevant documentation in the manual,
since now that we changed "trust" to "peer" a regular user cannot
connect to a newly initialized database using `psql -U postgres` (and is
good for security reasons); the user must be part of the "wheel" group
(or be authorized via sudoers in other ways) to be able to use `sudo su
postgres -s psql`
[...]
Thanks! Gio'
--
Giovanni Biscuolo
Xelera IT Infrastructures
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
prev parent reply other threads:[~2019-11-14 10:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-13 17:36 bug#38198: missing shell for postgresql system user Giovanni Biscuolo
2019-11-13 19:36 ` Gábor Boskovits
2019-11-14 10:02 ` Giovanni Biscuolo [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=878soiojx4.fsf@roquette.mug.biscuolo.net \
--to=g@xelera.eu \
--cc=38198-done@debbugs.gnu.org \
--cc=boskovits@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).