From: guix-patches--- via <guix-patches@gnu.org>
To: Mathieu Othacehe <othacehe@gnu.org>
Cc: 46249@debbugs.gnu.org, 46249-done@debbugs.gnu.org, ben@sturm.com.au
Subject: [bug#46249] [PATCH] Update documented default PostgreSQL socket-directory
Date: Tue, 02 Feb 2021 22:20:18 +1100 [thread overview]
Message-ID: <87r1lyu365.fsf@sturm.com.au> (raw)
In-Reply-To: <87y2g6an14.fsf@gnu.org>
On Tue, 02 Feb 2021, Mathieu Othacehe wrote:
> 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 for the quick follow-up Mathieu, that's very helpful.
While I'm bothering you, those comments "XXX: Remove when postgresql
default socket directory is changed to /var/run/postgresql" looked like
they could be might be redundant now. Is that the case?
Thanks again,
Ben
prev parent reply other threads:[~2021-02-02 11:21 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
2021-02-02 11:20 ` guix-patches--- via [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=87r1lyu365.fsf@sturm.com.au \
--to=guix-patches@gnu.org \
--cc=46249-done@debbugs.gnu.org \
--cc=46249@debbugs.gnu.org \
--cc=ben@sturm.com.au \
--cc=othacehe@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.
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).