Package Details: postgresql13 13.14-1

Git Clone URL: https://aur.archlinux.org/postgresql13.git (read-only, click to copy)
Package Base: postgresql13
Description: Sophisticated object-relational DBMS
Upstream URL: https://www.postgresql.org/
Licenses: custom:PostgreSQL
Conflicts: postgresql
Provides: postgresql
Submitter: msrd0
Maintainer: msrd0
Last Packager: msrd0
Votes: 3
Popularity: 0.000002
First Submitted: 2022-04-22 22:39 (UTC)
Last Updated: 2024-02-20 22:35 (UTC)

Dependencies (33)

Required by (344)

Sources (9)

Latest Comments

1 2 Next › Last »

msrd0 commented on 2023-12-20 21:27 (UTC)

@s_m Yeah that's a "new" feature of pacman (not really new but feels like it should still be experimental) that works only if you do a full system upgrade. The fact that the new version of icu needs to be installed so that you can build the new version of postgres is not really supported. So I guess you have two options: Obtain a newer build before upgrading icu (i.e. by using chroot to build) or remove, upgrade and reinstall postgres (no data gets lost, maybe you need to re-enable it with systemd, not sure actually).

s_m commented on 2023-12-20 17:56 (UTC)

How can I upgrade my system? Now I get this error:

sudo pacman -Syu
:: Synchronizing package databases... core is up to date extra is up to date community is up to date multilib is up to date archlinuxcn is up to date seblu is up to date :: Starting full system upgrade... resolving dependencies... looking for conflicting packages... error: failed to prepare transaction (could not satisfy dependencies) :: installing icu (74.2-1) breaks dependency 'libicui18n.so=73' required by postgresql13 :: installing icu (74.2-1) breaks dependency 'libicuuc.so=73' required by postgresql13 :: installing icu (74.2-1) breaks dependency 'libicudata.so=73' required by postgresql13

cmc commented on 2023-09-14 14:23 (UTC)

Excellent!!! Thank you for responding so amazingly quickly.

msrd0 commented on 2023-09-14 14:22 (UTC)

@cmc You are correct, postgresql seems to not support LLVM16. I have updated the package.

cmc commented on 2023-09-14 13:49 (UTC)

Please add dependency:

llvm15-libs

Explanation: llvm-libs has moved to v16, which results in the following hard-to-track error message when running queries:

could not load library "/usr/lib/postgresql/llvmjit.so": libLLVM-15.so:

This fixes the problem

pacman -S llvm15-libs

xeruf commented on 2022-07-03 17:31 (UTC) (edited on 2022-07-03 17:32 (UTC) by xeruf)

still getting two test failures :/

```sh
2 of 201 tests failed.

The differences that caused some tests to fail can be viewed in the file "/home/janek/.local/cache/yay/postgresql13/src/postgresql-13.7/src/test/regress/regression.diffs". A copy of the test summary that you see above is saved in the file "/home/janek/.local/cache/yay/postgresql13/src/postgresql-13.7/src/test/regress/regression.out".

make[1]: [GNUmakefile:132: check] Error 1 make[1]: Leaving directory '/home/janek/.local/cache/yay/postgresql13/src/postgresql-13.7/src/test/regress' make: [GNUmakefile:69: check] Error 2 make check failure: ./src/test/regress/regression.diffs diff -U3 /home/janek/.local/cache/yay/postgresql13/src/postgresql-13.7/src/test/regress/expected/collate.icu.utf8.out /home/janek/.local/cache/yay/postgresql13/src/postgresql-13.7/src/test/regress/results/collate.icu.utf8.out --- /home/janek/.local/cache/yay/postgresql13/src/postgresql-13.7/src/test/regress/expected/collate.icu.utf8.out 2022-05-09 21:16:30.000000000 +0000 +++ /home/janek/.local/cache/yay/postgresql13/src/postgresql-13.7/src/test/regress/results/collate.icu.utf8.out 2022-07-03 17:28:36.722967733 +0000 @@ -1035,6 +1035,9 @@ quote_literal(current_setting('lc_ctype')) || ');'; END $$; +ERROR: collations with different collate and ctype values are not supported by ICU +CONTEXT: SQL statement "CREATE COLLATION test1 (provider = icu, lc_collate = 'C', lc_ctype = 'en_IE.UTF-8');" +PL/pgSQL function inline_code_block line 3 at EXECUTE CREATE COLLATION test3 (provider = icu, lc_collate = 'en_US.utf8'); -- fail, need lc_ctype ERROR: parameter "lc_ctype" must be specified CREATE COLLATION testx (provider = icu, locale = 'nonsense'); / never fails with ICU / DROP COLLATION testx; @@ -1045,13 +1048,12 @@ collname

test0 - test1 test5 -(3 rows) +(2 rows)

ALTER COLLATION test1 RENAME TO test11; +ERROR: collation "test1" for encoding "UTF8" does not exist ALTER COLLATION test0 RENAME TO test11; -- fail -ERROR: collation "test11" already exists in schema "collate_tests" ALTER COLLATION test1 RENAME TO test22; -- fail ERROR: collation "test1" for encoding "UTF8" does not exist ALTER COLLATION test11 OWNER TO regress_test_role; @@ -1059,18 +1061,19 @@ ERROR: role "nonsense" does not exist ALTER COLLATION test11 SET SCHEMA test_schema; COMMENT ON COLLATION test0 IS 'US English'; +ERROR: collation "test0" for encoding "UTF8" does not exist SELECT collname, nspname, obj_description(pg_collation.oid, 'pg_collation') FROM pg_collation JOIN pg_namespace ON (collnamespace = pg_namespace.oid) WHERE collname LIKE 'test%' ORDER BY 1; collname | nspname | obj_description ----------+---------------+----------------- - test0 | collate_tests | US English test11 | test_schema | test5 | collate_tests | -(3 rows) +(2 rows)

DROP COLLATION test0, test_schema.test11, test5; +ERROR: collation "test0" for encoding "UTF8" does not exist DROP COLLATION test0; -- fail ERROR: collation "test0" for encoding "UTF8" does not exist DROP COLLATION IF EXISTS test0; @@ -1078,10 +1081,17 @@ SELECT collname FROM pg_collation WHERE collname LIKE 'test%'; collname

-(0 rows) + test11 + test5 +(2 rows)

DROP SCHEMA test_schema; +ERROR: cannot drop schema test_schema because other objects depend on it +DETAIL: collation test_schema.test11 depends on schema test_schema +HINT: Use DROP ... CASCADE to drop the dependent objects too. DROP ROLE regress_test_role; +ERROR: role "regress_test_role" cannot be dropped because some objects depend on it +DETAIL: owner of collation test_schema.test11 -- ALTER ALTER COLLATION "en-x-icu" REFRESH VERSION; NOTICE: version has not changed diff -U3 /home/janek/.local/cache/yay/postgresql13/src/postgresql-13.7/src/test/regress/expected/foreign_data.out /home/janek/.local/cache/yay/postgresql13/src/postgresql-13.7/src/test/regress/results/foreign_data.out --- /home/janek/.local/cache/yay/postgresql13/src/postgresql-13.7/src/test/regress/expected/foreign_data.out 2022-05-09 21:16:30.000000000 +0000 +++ /home/janek/.local/cache/yay/postgresql13/src/postgresql-13.7/src/test/regress/results/foreign_data.out 2022-07-03 17:28:42.712971483 +0000 @@ -5,10 +5,13 @@ -- Suppress NOTICE messages when roles don't exist SET client_min_messages TO 'warning'; DROP ROLE IF EXISTS regress_foreign_data_user, regress_test_role, regress_test_role2, regress_test_role_super, regress_test_indirect, regress_unprivileged_role; +ERROR: role "regress_test_role" cannot be dropped because some objects depend on it +DETAIL: owner of collation test_schema.test11 RESET client_min_messages; CREATE ROLE regress_foreign_data_user LOGIN SUPERUSER; SET SESSION AUTHORIZATION 'regress_foreign_data_user'; CREATE ROLE regress_test_role; +ERROR: role "regress_test_role" already exists CREATE ROLE regress_test_role2; CREATE ROLE regress_test_role_super SUPERUSER; CREATE ROLE regress_test_indirect; ==> ERROR: A failure occurred in check(). Aborting... -> error making: postgresql13

```

msrd0 commented on 2022-06-24 16:19 (UTC)

@Moxon I found the official version of the fix on the postgres 13 stable branch and applied that to the package, so we don't have to wait for the next release.

msrd0 commented on 2022-06-24 16:03 (UTC)

@gencom Please don't report duplicates. This is a known problem with the latest Perl version.

gencom commented on 2022-06-24 13:15 (UTC)

Build failed:
1 of 201 tests failed.

The differences that caused some tests to fail can be viewed in the file "/var/tmp/pamac-build-yun/postgresql13/src/postgresql-13.7/src/test/regress/regression.diffs". A copy of the test summary that you see above is saved in the file "/var/tmp/pamac-build-yun/postgresql13/src/postgresql-13.7/src/test/regress/regression.out".

make[1]: [GNUmakefile:132：check] 错误 1 make[1]: 离开目录“/var/tmp/pamac-build-yun/postgresql13/src/postgresql-13.7/src/test/regress” make: [GNUmakefile:69：check] 错误 2 make check failure: ./src/test/regress/regression.diffs diff -U3 /var/tmp/pamac-build-yun/postgresql13/src/postgresql-13.7/src/test/regress/expected/collate.linux.utf8.out /var/tmp/pamac-build-yun/postgresql13/src/postgresql-13.7/src/test/regress/results/collate.linux.utf8.out --- /var/tmp/pamac-build-yun/postgresql13/src/postgresql-13.7/src/test/regress/expected/collate.linux.utf8.out 2022-05-10 05:16:30.000000000 +0800 +++ /var/tmp/pamac-build-yun/postgresql13/src/postgresql-13.7/src/test/regress/results/collate.linux.utf8.out 2022-06-25 05:13:10.390191388 +0800 @@ -437,43 +437,38 @@

-- to_char SET lc_time TO 'tr_TR'; +ERROR: invalid value for parameter "lc_time": "tr_TR" SELECT to_char(date '2010-02-01', 'DD TMMON YYYY'); to_char

  • 01 ŞUB 2010
  • 01 FEB 2010 (1 row)

SELECT to_char(date '2010-02-01', 'DD TMMON YYYY' COLLATE "tr_TR"); to_char

  • 01 ŞUB 2010
  • 01 FEB 2010 (1 row)

SELECT to_char(date '2010-04-01', 'DD TMMON YYYY'); to_char

  • 01 NIS 2010
  • 01 APR 2010 (1 row)

SELECT to_char(date '2010-04-01', 'DD TMMON YYYY' COLLATE "tr_TR"); to_char

  • 01 NİS 2010
  • 01 APR 2010 (1 row)

-- to_date SELECT to_date('01 ŞUB 2010', 'DD TMMON YYYY'); - to_date

  • 02-01-2010 -(1 row) - +ERROR: invalid value "ŞUB" for "MON" +DETAIL: The given value did not match any of the allowed values for this field. SELECT to_date('01 Şub 2010', 'DD TMMON YYYY');
  • to_date
  • 02-01-2010 -(1 row) - +ERROR: invalid value "Şub" for "MON" +DETAIL: The given value did not match any of the allowed values for this field. SELECT to_date('1234567890ab 2010', 'TMMONTH YYYY'); -- fail ERROR: invalid value "1234567890ab" for "MONTH" DETAIL: The given value did not match any of the allowed values for this field. ==> 错误： 在 check() 中发生一个错误。 正在放弃...

msrd0 commented on 2022-06-22 14:05 (UTC)

@Moxon seems like they don't like the patch in its current form https://www.postgresql.org/message-id/630586.1654104622%40sss.pgh.pa.us. Also, they seem to have the intention to back-patch it to older versions, so this will likely be fixed in the next upstream release.

1 2 Next › Last »