postgresql13
No description set
- Developed at server:database:postgresql
- Sources inherited from project openSUSE:Factory
-
3
derived packages
- Download package
-
Checkout Package
osc -A https://api.opensuse.org checkout openSUSE:Leap:16.0:FactoryCandidates/postgresql13 && cd $_
- Create Badge
Refresh
Refresh
Source Files
Filename | Size | Changed |
---|---|---|
0001-jit-Workaround-potential-datalayout-mismatch- |
0000003156 3.08 KB | |
_constraints | 0000000245 245 Bytes | |
baselibs.conf | 0000000174 174 Bytes | |
postgresql-13.14.tar.bz2 | 0021584146 20.6 MB | |
postgresql-13.14.tar.bz2.sha256 | 0000000091 91 Bytes | |
postgresql-conf.patch | 0000001086 1.06 KB | |
postgresql-llvm-optional.patch | 0000000562 562 Bytes | |
postgresql-plperl-keep-rpath.patch | 0000001307 1.28 KB | |
postgresql-rpmlintrc | 0000000268 268 Bytes | |
postgresql-testsuite-keep-results-file.patch | 0000000376 376 Bytes | |
postgresql-var-run-socket.patch | 0000001698 1.66 KB | |
postgresql13.changes | 0000014750 14.4 KB | |
postgresql13.spec | 0000028807 28.1 KB |
Revision 27 (latest revision is 30)
Ana Guerrero (anag+factory)
accepted
request 1145272
from
Reinhard Max (rmax)
(revision 27)
- Upgrade to 13.14: * bsc#1219679, CVE-2024-0985: Tighten security restrictions within REFRESH MATERIALIZED VIEW CONCURRENTLY. One step of a concurrent refresh command was run under weak security restrictions. If a materialized view's owner could persuade a superuser or other high-privileged user to perform a concurrent refresh on that view, the view's owner could control code executed with the privileges of the user running REFRESH. Fix things so that all user-determined code is run as the view's owner, as expected * If you use GIN indexes, you may need to reindex after updating to this release. * LLVM 18 is now supported. * https://www.postgresql.org/docs/release/13.4/
Comments 0