public inbox for [email protected]
help / color / mirror / Atom feedFrom: Tom Lane <[email protected]>
To: Cihat Küçükbağrıaçık <[email protected]>
Cc: [email protected]
Subject: Re: Passwordcheck Extension Not Installing
Date: Mon, 10 Feb 2025 10:53:48 -0500
Message-ID: <[email protected]> (raw)
In-Reply-To: <CAAqOvVNWc9y2WcxqxW9hqD3wX=R3whb6nK0WU45K4gw2zEqjGg@mail.gmail.com>
References: <CAAqOvVMd4nUJVL0iXcMK4HwLm+UA2h_EqEfbzWysxTv45UMGDw@mail.gmail.com>
<[email protected]>
<CAAqOvVNWc9y2WcxqxW9hqD3wX=R3whb6nK0WU45K4gw2zEqjGg@mail.gmail.com>
=?UTF-8?B?Q2loYXQgS8O8w6fDvGtiYcSfcsSxYcOnxLFr?= <[email protected]> writes:
> I have also observed that the *passwordcheck.so* file exists in the
> *"/usr/lib/postgresql/17/lib/"* directory. It seems that, for some reason,
> when the PostgreSQL service starts, it is unable to read the
> *passwordcheck.so* file and create the *passwordcheck.control* file in the
> *"/usr/share/postgresql/17/extension/"* directory.
No, you misunderstand the process. The .control file is one of the
distributed files for an extension; the server has no ability to
create one.
What we both missed is that *passwordcheck is not an extension*.
It has no SQL-visible objects. It's just a shared library that
you must preload into the server, as per its documentation.
regards, tom lane
view thread (3+ messages)
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected]
Subject: Re: Passwordcheck Extension Not Installing
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox