From: Mathieu Othacehe <othacehe@gnu.org>
To: 46249@debbugs.gnu.org
Cc: Ben Sturmfels <ben@sturm.com.au>, 46249-done@debbugs.gnu.org
Subject: [bug#46249] [PATCH] Update documented default PostgreSQL socket-directory
Date: Tue, 02 Feb 2021 09:31:35 +0100 [thread overview]
Message-ID: <87y2g6an14.fsf@gnu.org> (raw)
In-Reply-To: <87wnvrtjpv.fsf@sturm.com.au> (guix-patches@gnu.org's message of "Tue, 02 Feb 2021 11:08:12 +1100")
Hey Ben,
> It looks like the documented default for PostgreSQL's socket-directory
> variable should be "/var/run/postgresql", when it's currently
> "/var/lib/postgresql" (the data directory). I've attached a patch.
> Here's the original commit (thanks lfam for the IRC help):
That's a dumb mistake on my part, thanks for fixing it.
> https://git.savannah.gnu.org/cgit/guix.git/commit/?id=6c0679215f4ffa534c1eb2e8c8a6e043a0c993fe
>
> Also noticed that since a recent reconfigure, my `psql` and `createdb`
> commands now need an explicit `-h /var/run/postgresql` argument to
> connect to the local database where one wasn't needed before - they look
> in /tmp by default.
Yes when the socket directory is enabled in PostgreSQL those tools try
to use it but with the default directory set to "/tmp". I have pushed a
patch on core-updates to set the default socket directory to
"/var/run/postgresql" like most of the other distributions.
In the meantime you can set the "socket-directory" field of
"postgresql-config-file" to #f to restore the previous behaviour.
Thanks,
Mathieu
next prev parent reply other threads:[~2021-02-02 8:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-02 0:08 [bug#46249] [PATCH] Update documented default PostgreSQL socket-directory guix-patches--- via
2021-02-02 8:31 ` Mathieu Othacehe [this message]
2021-02-02 11:20 ` guix-patches--- via
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y2g6an14.fsf@gnu.org \
--to=othacehe@gnu.org \
--cc=46249-done@debbugs.gnu.org \
--cc=46249@debbugs.gnu.org \
--cc=ben@sturm.com.au \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.