From: "Gábor Boskovits" <boskovits@gmail.com>
To: Pierre Neidhardt <mail@ambrevar.xyz>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: Doc bug: Postgres account not available
Date: Mon, 8 Jun 2020 07:40:15 +0200 [thread overview]
Message-ID: <CAE4v=piPv8Za5C2jCC=JZP-p12uchx2AqOL_ZCZyZFPWpCP_kA@mail.gmail.com> (raw)
In-Reply-To: <87o8qeiu8f.fsf@ambrevar.xyz>
Hello Pierre,
This has been this way for a while. It took me some time to find it
out also. I guess that documenting it would be fine.
Most of the times I finally end up adding a shell to the account, but
keeping it this way is a sane default when you automanage your
database.
Pierre Neidhardt <mail@ambrevar.xyz> ezt írta (időpont: 2020. máj.
23., Szo, 16:47):
>
> Hi!
>
> Apparently our Postgres service changed a little bit recently. While it
> was easy to setup in the past, this week it cost me a few hours, trying
> to figure out how to do a simple thing like
>
> --8<---------------cut here---------------start------------->8---
> $ psql -U postgres
> psql: FATAL: Peer authentication failed for user "postgres"
> --8<---------------cut here---------------end--------------->8---
>
> Eventually, I discovered https://issues.guix.info/38198.
> Turns out the authentication policy is now "peer" and the shell-less
> 'postgres' user cannot be used without a shell.
>
> As such, to administrate PostgresQL we need first to switch to the
> postgres user as follows:
>
> --8<---------------cut here---------------start------------->8---
> sudo su postgres -s psql
> --8<---------------cut here---------------end--------------->8---
>
> This was not a very obvious find on the Internet.
> Can we make this easier? The above thread suggests to leave the setup
> as is and to document it.
>
> Thoughts? Gábor, Giovanni?
>
> --
> Pierre Neidhardt
> https://ambrevar.xyz/
Best regards,
g_bor
--
OpenPGP Key Fingerprint: 7988:3B9F:7D6A:4DBF:3719:0367:2506:A96C:CF63:0B21
next prev parent reply other threads:[~2020-06-08 5:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-23 14:47 Doc bug: Postgres account not available Pierre Neidhardt
2020-06-08 5:40 ` Gábor Boskovits [this message]
2020-06-10 9:32 ` Pierre Neidhardt
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='CAE4v=piPv8Za5C2jCC=JZP-p12uchx2AqOL_ZCZyZFPWpCP_kA@mail.gmail.com' \
--to=boskovits@gmail.com \
--cc=help-guix@gnu.org \
--cc=mail@ambrevar.xyz \
/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.
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).