public inbox for [email protected]  

help / color / mirror / Atom feed

From: Christoph Berg <[email protected]>
To: Peter Eisentraut <[email protected]>
Cc: [email protected]
Cc: David E. Wheeler <[email protected]>
Subject: extension_control_path and "directory"
Date: Wed, 23 Apr 2025 11:39:32 +0200
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>

Re: Peter Eisentraut
> The new GUC extension_control_path specifies a path to look for
> extension control files.  The default value is $system, which looks in
> the compiled-in location, as before.

Is the expectation that this also works for the extension "directory"?

semver is still failing because it's shipping its .sql files in a
separate directory:

2025-04-23 09:06:24.864 UTC [422345] myon@contrib_regression ERROR:  could not open directory "/usr/share/postgresql/18/semver": No such file or directory
2025-04-23 09:06:24.864 UTC [422345] myon@contrib_regression STATEMENT:  CREATE EXTENSION semver;

$ cat debian/postgresql-18-semver/usr/share/postgresql/18/extension/semver.control
# semver extension
comment = 'Semantic version data type'
default_version = '0.40.0'

directory = 'semver'
module_pathname = '$libdir/semver'
relocatable = true

$ ls debian/postgresql-18-semver/usr/share/postgresql/18/semver/
semver--0.10.0--0.11.0.sql  semver--0.17.0--0.20.0.sql  semver--0.30.0--0.31.0.sql  semver--0.32.1--0.40.0.sql
semver--0.11.0--0.12.0.sql  semver--0.20.0--0.21.0.sql  semver--0.3.0--0.4.0.sql    semver--0.40.0.sql
semver--0.12.0--0.13.0.sql  semver--0.21.0--0.22.0.sql  semver--0.31.0--0.31.1.sql  semver--0.5.0--0.10.0.sql
semver--0.13.0--0.15.0.sql  semver--0.2.1--0.2.4.sql    semver--0.31.1--0.31.2.sql  semver.sql
semver--0.15.0--0.16.0.sql  semver--0.22.0--0.30.0.sql  semver--0.31.2--0.32.0.sql  semver--unpackaged--0.2.1.sql
semver--0.16.0--0.17.0.sql  semver--0.2.4--0.3.0.sql    semver--0.32.0--0.32.1.sql

Christoph

view thread (20+ messages)  latest in thread

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], [email protected]
  Subject: Re: extension_control_path and "directory"
  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