From: Gary Johnson <lambdatronic@disroot.org>
To: Julien Lepiller <julien@lepiller.eu>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: How do I correctly relocate PostGIS control files?
Date: Tue, 03 Nov 2020 19:38:26 -0500 [thread overview]
Message-ID: <87k0v2ez25.fsf@disroot.org> (raw)
In-Reply-To: <58ED72A6-E00F-4E9F-A111-6E4C082212D3@lepiller.eu>
Julien Lepiller <julien@lepiller.eu> writes:
> The service simply builds a union-build of the postgis and postgresql
> packages, because postgresql looks for its extensions in the directory
> it's run from.
>
> It could be that this behavior changed, or that the postgis package
> doesn't build its extension as expected.
>
> To cgeck these hypothesis: can you check the error message contains
> the store path of the union (as opposed to only postresql). You should
> be able to find some of postgis files there in addition to postgresql
> files.
gjohnson@euclid ~ $ guix package -p /run/current-system/profile -I
...
postgis 3.0.2 out /gnu/store/0cb4sf18w2i9f0b79kyrli7fx3i63c4s-postgis-3.0.2
postgresql 13.0 out /gnu/store/8m48v5132qpmxim9s4g9vca59qgay2d9-postgresql-13.0
gjohnson@euclid ~ $ ls /gnu/store/8m48v5132qpmxim9s4g9vca59qgay2d9-postgresql-13.0/share/extension/
adminpack--1.0--1.1.sql btree_gist--1.3--1.4.sql dict_int.control intagg--1.0--1.1.sql pageinspect--1.1--1.2.sql pg_stat_statements--1.0--1.1.sql pgcrypto--1.1--1.2.sql seg--1.1--1.2.sql
adminpack--1.0.sql btree_gist--1.4--1.5.sql dict_xsyn--1.0.sql intagg--1.1.sql pageinspect--1.2--1.3.sql pg_stat_statements--1.1--1.2.sql pgcrypto--1.2--1.3.sql seg--1.1.sql
adminpack--1.1--2.0.sql btree_gist.control dict_xsyn.control intagg.control pageinspect--1.3--1.4.sql pg_stat_statements--1.2--1.3.sql pgcrypto--1.3.sql seg--1.2--1.3.sql
adminpack--2.0--2.1.sql citext--1.0--1.1.sql earthdistance--1.0--1.1.sql intarray--1.0--1.1.sql pageinspect--1.4--1.5.sql pg_stat_statements--1.3--1.4.sql pgcrypto.control seg.control
adminpack.control citext--1.1--1.2.sql earthdistance--1.1.sql intarray--1.1--1.2.sql pageinspect--1.5--1.6.sql pg_stat_statements--1.4--1.5.sql pgrowlocks--1.0--1.1.sql sslinfo--1.0--1.1.sql
amcheck--1.0--1.1.sql citext--1.2--1.3.sql earthdistance.control intarray--1.2--1.3.sql pageinspect--1.5.sql pg_stat_statements--1.4.sql pgrowlocks--1.1--1.2.sql sslinfo--1.1--1.2.sql
amcheck--1.0.sql citext--1.3--1.4.sql file_fdw--1.0.sql intarray--1.2.sql pageinspect--1.6--1.7.sql pg_stat_statements--1.5--1.6.sql pgrowlocks--1.2.sql sslinfo--1.2.sql
amcheck--1.1--1.2.sql citext--1.4--1.5.sql file_fdw.control intarray.control pageinspect--1.7--1.8.sql pg_stat_statements--1.6--1.7.sql pgrowlocks.control sslinfo.control
amcheck.control citext--1.4.sql fuzzystrmatch--1.0--1.1.sql isn--1.0--1.1.sql pageinspect.control pg_stat_statements--1.7--1.8.sql pgstattuple--1.0--1.1.sql tablefunc--1.0.sql
autoinc--1.0.sql citext--1.5--1.6.sql fuzzystrmatch--1.1.sql isn--1.1--1.2.sql pg_buffercache--1.0--1.1.sql pg_stat_statements.control pgstattuple--1.1--1.2.sql tablefunc.control
autoinc.control citext.control fuzzystrmatch.control isn--1.1.sql pg_buffercache--1.1--1.2.sql pg_trgm--1.0--1.1.sql pgstattuple--1.2--1.3.sql tcn--1.0.sql
bloom--1.0.sql cube--1.0--1.1.sql hstore--1.0--1.1.sql isn.control pg_buffercache--1.2--1.3.sql pg_trgm--1.1--1.2.sql pgstattuple--1.3--1.4.sql tcn.control
bloom.control cube--1.1--1.2.sql hstore--1.1--1.2.sql lo--1.0--1.1.sql pg_buffercache--1.2.sql pg_trgm--1.2--1.3.sql pgstattuple--1.4--1.5.sql tsm_system_rows--1.0.sql
btree_gin--1.0--1.1.sql cube--1.2--1.3.sql hstore--1.2--1.3.sql lo--1.1.sql pg_buffercache.control pg_trgm--1.3--1.4.sql pgstattuple--1.4.sql tsm_system_rows.control
btree_gin--1.0.sql cube--1.2.sql hstore--1.3--1.4.sql lo.control pg_freespacemap--1.0--1.1.sql pg_trgm--1.3.sql pgstattuple.control tsm_system_time--1.0.sql
btree_gin--1.1--1.2.sql cube--1.3--1.4.sql hstore--1.4--1.5.sql ltree--1.0--1.1.sql pg_freespacemap--1.1--1.2.sql pg_trgm--1.4--1.5.sql plpgsql--1.0.sql tsm_system_time.control
btree_gin--1.2--1.3.sql cube.control hstore--1.4.sql ltree--1.1--1.2.sql pg_freespacemap--1.1.sql pg_trgm.control plpgsql.control unaccent--1.0--1.1.sql
btree_gin.control dblink--1.0--1.1.sql hstore--1.5--1.6.sql ltree--1.1.sql pg_freespacemap.control pg_visibility--1.0--1.1.sql postgres_fdw--1.0.sql unaccent--1.1.sql
btree_gist--1.0--1.1.sql dblink--1.1--1.2.sql hstore--1.6--1.7.sql ltree.control pg_prewarm--1.0--1.1.sql pg_visibility--1.1--1.2.sql postgres_fdw.control unaccent.control
btree_gist--1.1--1.2.sql dblink--1.2.sql hstore.control moddatetime--1.0.sql pg_prewarm--1.1--1.2.sql pg_visibility--1.1.sql refint--1.0.sql uuid-ossp--1.0--1.1.sql
btree_gist--1.2--1.3.sql dblink.control insert_username--1.0.sql moddatetime.control pg_prewarm--1.1.sql pg_visibility.control refint.control uuid-ossp--1.1.sql
btree_gist--1.2.sql dict_int--1.0.sql insert_username.control pageinspect--1.0--1.1.sql pg_prewarm.control pgcrypto--1.0--1.1.sql seg--1.0--1.1.sql uuid-ossp.control
So...unfortunately there are no postgis files in the postgresql directory.
> For the second hypothesis, can you find the postgis.control file in the postgis package itself?
gjohnson@euclid ~ $ tree /gnu/store/0cb4sf18w2i9f0b79kyrli7fx3i63c4s-postgis-3.0.2
/gnu/store/0cb4sf18w2i9f0b79kyrli7fx3i63c4s-postgis-3.0.2
├── bin
│ ├── pgsql2shp
│ ├── raster2pgsql
│ └── shp2pgsql
├── lib
│ ├── address_standardizer-3.so
│ ├── postgis-3.so
│ ├── postgis_raster-3.so
│ └── postgis_topology-3.so
└── share
├── contrib
├── doc
└── extension
├── address_standardizer.control
├── address_standardizer_data_us.control
├── postgis.control
├── postgis_raster.control
├── postgis_tiger_geocoder.control
├── postgis_topology.control
├── ...
Yes. All of the expected postgis files can be found in the postgis
package.
So it looks like there is an issue with the way postgresql-service-type
installs its extensions. How can we correct this?
Thanks in advance,
Gary
--
GPG Key ID: 7BC158ED
Use `gpg --search-keys lambdatronic' to find me
Protect yourself from surveillance: https://emailselfdefense.fsf.org
=======================================================================
() ascii ribbon campaign - against html e-mail
/\ www.asciiribbon.org - against proprietary attachments
Please avoid sending me MS-Office attachments.
See http://www.gnu.org/philosophy/no-word-attachments.html
next prev parent reply other threads:[~2020-11-04 1:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-02 22:40 How do I correctly relocate PostGIS control files? Gary Johnson
2020-11-03 2:23 ` Julien Lepiller
2020-11-04 0:38 ` Gary Johnson [this message]
2020-11-09 23:56 ` Gary Johnson
2020-11-10 1:45 ` Julien Lepiller
2020-11-10 2:14 ` Carlo Zancanaro
2020-11-10 17:45 ` Gary Johnson
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=87k0v2ez25.fsf@disroot.org \
--to=lambdatronic@disroot.org \
--cc=help-guix@gnu.org \
--cc=julien@lepiller.eu \
/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).