Merge postgresql-16 from Debian unstable for oracular
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
postgresql-16 (Ubuntu) |
New
|
Undecided
|
Athos Ribeiro |
Bug Description
Upstream: tbd
Debian: 16.2-2
Ubuntu: 16.2-1ubuntu4
Debian does new releases regularly, so it's likely there will be newer versions available before FF that we can pick up if this merge is done later in the cycle.
If it turns out this needs a sync rather than a merge, please change the tag 'needs-merge' to 'needs-sync', and (optionally) update the title as desired.
If this merge pulls in a new upstream version, also consider adding an entry to the Oracular Release Notes: https:/
### New Debian Changes ###
postgresql-16 (16.2-2) unstable; urgency=medium
* Add Build-Profile pkg.postgresql.
-- Christoph Berg <email address hidden> Mon, 18 Mar 2024 17:01:50 +0100
postgresql-16 (16.2-1) unstable; urgency=medium
* New upstream version.
* Tighten security restrictions within REFRESH MATERIALIZED VIEW
CONCURRENTLY (Heikki Linnakangas)
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.
The only known exploit for this error does not work in PostgreSQL 16.0
and later, so it may be that v16 is not vulnerable in practice.
The PostgreSQL Project thanks Pedro Gallegos for reporting this problem.
(
* Add Swedish debconf translation by Martin Bagge and Anders Jonsson.
Thanks! (Closes: #1059170)
-- Christoph Berg <email address hidden> Tue, 06 Feb 2024 13:27:57 +0100
postgresql-16 (16.1-1) unstable; urgency=medium
* New upstream version.
* Fix handling of unknown-type arguments in DISTINCT 'any' aggregate
functions (Tom Lane)
This error led to a text-type value being interpreted as an unknown-type
value (that is, a zero-terminated string) at runtime. This could result
in disclosure of server memory following the text value.
The PostgreSQL Project thanks Jingzhou Fu for reporting this problem.
(
* Detect integer overflow while computing new array dimensions
(Tom Lane)
When assigning new elements to array subscripts that are outside the
current array bounds, an undetected integer overflow could occur in edge
cases. Memory stomps that are potentially exploitable for arbitrary
code execution are possible, and so is disclosure of server memory.
The PostgreSQL Project thanks Pedro Gallegos for reporting this problem.
(
* Prevent the pg_signal_backend role from signalling background workers
and autovacuum processes (Noah Misch, Jelte Fennema-Nio)
The documentation says that pg_signal_backend
cannot issue signals to superuser-owned processes. It was able to
signal these background processes, though, because they advertise a
role OID of zero. Treat that as indicating superuser ownership.
The security implications of cancelling one of these process types
are fairly small so far as the core code goes (we'll just start
another one), but extensions might add background workers that are
more vulnerable.
Also ensure that the is_superuser parameter is set correctly in such
processes. No specific security consequences are known for that
oversight, but it might be significant for some extensions.
The PostgreSQL Project thanks Hemanth Sandrana and Mahendrakar
Srinivasarao for reporting this problem. (CVE-2023-5870)
* Fix misbehavior during recursive page split in GiST index build
(Heikki Linnakangas)
Fix a case where the location of a page downlink was incorrectly
tracked, and introduce some logic to allow recovering from such
situations rather than silently doing the wrong thing. This error could
result in incorrect answers from subsequent index searches. It may be
advisable to reindex all GiST indexes after installing this update.
* Prevent de-duplication of btree index entries for interval columns
There are interval values that are distinguishable but compare equal,
for example 24:00:00 and 1 day. This breaks assumptions made by btree
de-
de-
index-only scans. Moreover, after updating amcheck will report an error
for almost all such indexes. Users should reindex any btree indexes on
interval columns.
* Use default LLVM version; package is now compatible with LLVM 16.
* Rebase debian/
-- Christoph Berg <email address hidden> Tue, 07 Nov 2023 14:18:31 +0100
postgresql-16 (16.0-2) unstable; urgency=medium
### Old Ubuntu Delta ###
postgresql-16 (16.2-1ubuntu4) noble; urgency=high
* No change rebuild against libllvm17t64.
-- Julian Andres Klode <email address hidden> Mon, 08 Apr 2024 16:48:10 +0200
postgresql-16 (16.2-1ubuntu3) noble; urgency=medium
* No-change rebuild for CVE-2024-3094
-- Steve Langasek <email address hidden> Sun, 31 Mar 2024 00:13:40 +0000
postgresql-16 (16.2-1ubuntu2) noble; urgency=medium
* No-change rebuild against libperl5.38t64
-- Steve Langasek <email address hidden> Sat, 09 Mar 2024 18:23:15 +0000
postgresql-16 (16.2-1ubuntu1) noble; urgency=medium
* d/control: Pin llvm-17 on Build-Depends. The package currently
FTBFS withg llvm-18.
-- Sergio Durigan Junior <email address hidden> Mon, 04 Mar 2024 14:56:24 -0500
postgresql-16 (16.2-1build1) noble; urgency=medium
* No-change rebuild for perlapi5.38t64.
-- Matthias Klose <email address hidden> Sun, 03 Mar 2024 05:34:54 +0100
Changed in postgresql-16 (Ubuntu): | |
milestone: | none → ubuntu-24.07 |
Changed in postgresql-16 (Ubuntu): | |
assignee: | nobody → Athos Ribeiro (athos-ribeiro) |