Package Details: postgresql15-docs 15.8-1

Git Clone URL: https://aur.archlinux.org/postgresql15.git (read-only, click to copy)
Package Base: postgresql15
Description: HTML documentation for PostgreSQL
Upstream URL: https://www.postgresql.org/
Licenses: custom:PostgreSQL
Provides: postgresql
Submitter: mrechte
Maintainer: mrechte
Last Packager: mrechte
Votes: 2
Popularity: 0.98
First Submitted: 2023-12-08 11:01 (UTC)
Last Updated: 2024-08-13 06:41 (UTC)

Dependencies (14)

Required by (389)

Sources (9)

Pinned Comments

mrechte commented on 2023-12-08 11:02 (UTC) (edited on 2023-12-26 14:39 (UTC) by mrechte)

Introduction

This version may cohabit with other major versions, including the official one.

Data directory is /var/lib/postgres/data15

Initialize the database
su - postgres
. /opt/postgresql15/bin/pgenv.sh
initdb -k
Start the service
systemctl start postgresql15
Use the service
. /opt/postgresql15/bin/pgenv.sh
psql -U postgres

Latest Comments

1 2 Next › Last »

s_m commented on 2025-02-05 20:59 (UTC) (edited on 2025-02-05 21:00 (UTC) by s_m)

First of all, thanks a lot for this package!

When I install it, I notice that the version is::

$ . /opt/postgresql15/bin/pgenv.sh # postgresql  
$  psql -V 
psql (PostgreSQL) 15.8

Is it possible to bump the version to 15.10? See https://www.postgresql.org/support/versioning/ :

We recommend that users always run the current minor release associated with their major version.

mrechte commented on 2024-09-23 10:26 (UTC) (edited on 2024-09-23 10:51 (UTC) by mrechte)

@Markus.N, I have the same problem not only with PG15 but also with PG16.

On Arch:
# set datestyle to postgres;
SET

# set timezone to 'Europe/Paris';
SET

# SELECT DATE_TRUNC('MILLENNIUM', DATE '1970-03-20');
          date_trunc          
------------------------------
 Thu Jan 01 00:00:00 1001 LMT
(1 ligne)


# set timezone to 'PST8PDT';
SET

# SELECT DATE_TRUNC('MILLENNIUM', DATE '1970-03-20');
          date_trunc          
------------------------------
 Thu Jan 01 00:00:00 1001 LMT
(1 ligne)
On RHEL9
# set timezone to 'Europe/Paris';
SET

# SELECT DATE_TRUNC('MILLENNIUM', DATE '1970-03-20');
          date_trunc          
------------------------------
 Thu 01 Jan 00:00:00 1001 LMT
(1 ligne)

# set timezone to 'PST8PDT';
SET

# SELECT DATE_TRUNC('MILLENNIUM', DATE '1970-03-20');
          date_trunc          
------------------------------
 Thu 01 Jan 00:00:00 1001 PST
(1 ligne)

You may use makepg --nocheck to by-pass the tests.

Markus.N commented on 2024-09-12 23:10 (UTC)

I can't build the current version. The regression tests fail (left out all that was ok):

 +++ regress check in src/test/regress +++
 ============== creating temporary instance            ==============
 ============== initializing database system           ==============
 ============== starting postmaster                    ==============
 running on port 51704 with PID 773602
 ============== creating database "regression"         ==============
 CREATE DATABASE
 ALTER DATABASE
 ALTER DATABASE
 ALTER DATABASE
 ALTER DATABASE
 ALTER DATABASE
 ALTER DATABASE
 ============== running regression test queries        ==============
 parallel group (19 tests):  line numerology lseg circle path macaddr8 time macaddr timetz inet date interval strings point timestamp timestamptz polygon multirangetypes box
      date                         ... FAILED      105 ms
      timestamptz                  ... FAILED      392 ms
 parallel group (13 tests):  unicode comments misc_sanity tstypes xid expressions mvcc geometry type_sanity horology opr_sanity database regex
      horology                     ... FAILED      338 ms
 ============== shutting down postmaster               ==============

 ========================
  3 of 213 tests failed. 
 ========================

Unfortunately, I can't go on with the currently installed version of the package due to changed libs in the base system.

mrechte commented on 2024-07-24 15:20 (UTC)

Release 2. Fixes xml regression test.

DimaCit commented on 2024-07-20 16:16 (UTC)

@mrechte I had the same issue as msrd0. The problem went away after I downgraded the package libxml2 to version 2.12.7.

hschletz commented on 2024-07-17 11:19 (UTC) (edited on 2024-07-17 11:34 (UTC) by hschletz)

I ran into the same build problem. Seems to be an occasional problem with libxml. Since I don't use the XML functionality, I removed the --with-libxml and --with-libxslt flags, and the tests ran without errors.

Warning: Upon reinstallation, the package suggested a dump-and-restore, possibly because of the removed functionality. It's a dev system without valuable data, and the databases kept working, but on a production database, it's advisable to create a dump before installing the modified package and restore afterwards.

Incorporating this change might be problematic because of the functionality loss, but people who don't use XML in their databases and want to run the tests can remove the lines manually.

fboerman commented on 2024-06-23 14:03 (UTC)

I have the same build error as @msrd0

mrechte commented on 2024-06-15 14:26 (UTC) (edited on 2024-06-15 14:27 (UTC) by mrechte)

@msrd0 I just recompiled. Tests passed OK. I cannot reproduce. You may use makepg --nocheck

msrd0 commented on 2024-06-14 09:35 (UTC)

The package fails to compile for me since the last update:

make check failure: ./src/test/regress/regression.diffs
diff -U3 /home/msrd0/.cache/yay/postgresql15/src/postgresql-15.7/src/test/regress/expected/xml.out /home/msrd0/.cache/yay/postgresql15/src/postgresql-15.7/src/test/regress/results/xml.out
--- /home/msrd0/.cache/yay/postgresql15/src/postgresql-15.7/src/test/regress/expected/xml.out   2024-05-06 22:23:18.000000000 +0200
+++ /home/msrd0/.cache/yay/postgresql15/src/postgresql-15.7/src/test/regress/results/xml.out    2024-06-14 11:26:47.085270807 +0200
@@ -223,23 +223,13 @@
 DETAIL:  line 1: xmlParseEntityRef: no name
 <invalidentity>&</invalidentity>
                 ^
-line 1: chunk is not well balanced
-<invalidentity>&</invalidentity>
-                                ^
 SELECT xmlparse(content '<undefinedentity>&idontexist;</undefinedentity>');
 ERROR:  invalid XML content
 DETAIL:  line 1: Entity 'idontexist' not defined
 <undefinedentity>&idontexist;</undefinedentity>
                              ^
-line 1: chunk is not well balanced
-<undefinedentity>&idontexist;</undefinedentity>
-                                               ^
 SELECT xmlparse(content '<invalidns xmlns=''&lt;''/>');
-         xmlparse
----------------------------
- <invalidns xmlns='&lt;'/>
-(1 row)
-
+ERROR:  invalid XML content
 SELECT xmlparse(content '<relativens xmlns=''relative''/>');
             xmlparse
 --------------------------------
@@ -254,15 +244,8 @@
 line 1: Opening and ending tag mismatch: twoerrors line 1 and unbalanced
 <twoerrors>&idontexist;</unbalanced>
                                     ^
-line 1: chunk is not well balanced
-<twoerrors>&idontexist;</unbalanced>
-                                    ^
 SELECT xmlparse(content '<nosuchprefix:tag/>');
-      xmlparse
----------------------
- <nosuchprefix:tag/>
-(1 row)
-
+ERROR:  invalid XML content
 SELECT xmlparse(document '   ');
 ERROR:  invalid XML document
 DETAIL:  line 1: Start tag expected, '<' not found
@@ -992,15 +975,13 @@
 -- error messages, we suppress the DETAIL in this test.
 \set VERBOSITY terse
 SELECT xpath('/*', '<invalidns xmlns=''&lt;''/>');
-ERROR:  could not parse XML document
+ERROR:  invalid XML content at character 20
 \set VERBOSITY default
 -- Again, the XML isn't well-formed for namespace purposes
 SELECT xpath('/*', '<nosuchprefix:tag/>');
-ERROR:  could not parse XML document
-DETAIL:  line 1: Namespace prefix nosuchprefix on tag is not defined
-<nosuchprefix:tag/>
-                 ^
-CONTEXT:  SQL function "xpath" statement 1
+ERROR:  invalid XML content
+LINE 1: SELECT xpath('/*', '<nosuchprefix:tag/>');
+                           ^
 -- XPath deprecates relative namespaces, but they're not supposed to
 -- throw an error, only a warning.
 SELECT xpath('/*', '<relativens xmlns=''relative''/>');
==> ERROR: A failure occurred in check().
    Aborting...
 -> error making: postgresql15-exit status 4

mrechte commented on 2024-02-21 16:18 (UTC)

@hschletz thanks for reporting. I though I had already fixed the issue. This should be OK now.

1 2 Next › Last »