unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Pierre Neidhardt <mail@ambrevar.xyz>
To: help-guix@gnu.org
Subject: Doc bug: Postgres account not available
Date: Sat, 23 May 2020 16:47:12 +0200	[thread overview]
Message-ID: <87o8qeiu8f.fsf@ambrevar.xyz> (raw)

[-- Attachment #1: Type: text/plain, Size: 1089 bytes --]

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/

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

             reply	other threads:[~2020-05-23 14:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-23 14:47 Pierre Neidhardt [this message]
2020-06-08  5:40 ` Doc bug: Postgres account not available Gábor Boskovits
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=87o8qeiu8f.fsf@ambrevar.xyz \
    --to=mail@ambrevar.xyz \
    --cc=help-guix@gnu.org \
    /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).