Skip to content

[pull] master from postgres:master #72

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Jun 7, 2025
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
55 changes: 34 additions & 21 deletions doc/src/sgml/release-18.sgml
Original file line number Diff line number Diff line change
Expand Up @@ -53,6 +53,24 @@

<itemizedlist>

<!--
Author: Peter Eisentraut <[email protected]>
2024-10-16 [04bec894a04] initdb: Change default to using data checksums.
-->

<listitem>
<para>
Change initdb default to enable data checksums
<ulink url="&commit_baseurl;04bec894a04">&sect;</ulink>
</para>

<para>
Checksums can be disabled with the new initdb option --no-data-checksums.
pg_upgrade requires matching cluster checksum settings, so this new
option can be useful to upgrade non-checksum old clusters.
</para>
</listitem>

<!--
Author: Tom Lane <[email protected]>
2025-01-16 [d7674c9fa] Seek zone abbreviations in the IANA data before timezone
Expand Down Expand Up @@ -139,6 +157,22 @@ Previously ALTER TABLE SET [UN]LOGGED did nothing, and the creation of an unlogg
</para>
</listitem>

<!--
Author: Tom Lane <[email protected]>
2025-01-23 [01463e1cc] Ensure that AFTER triggers run as the instigating user.
-->

<listitem>
<para>
Execute AFTER triggers as the role that was active when trigger events were queued (Laurenz Albe)
</para>

<para>
Previously such triggers were run as the role that was active at trigger execution time (e.g., at COMMIT). This is significant for cases where the role is changed between queue time and
transaction commit.
</para>
</listitem>

<!--
Author: Fujii Masao <[email protected]>
2024-09-12 [fefa76f70] Remove old RULE privilege completely.
Expand Down Expand Up @@ -192,27 +226,6 @@ Change pg_backend_memory_contexts.level and pg_log_backend_memory_contexts() to
<para>
These were previously zero-based.
</para>
</listitem>

<!--
Author: Peter Eisentraut <[email protected]>
2024-10-16 [04bec894a04] initdb: Change default to using data checksums.
-->

<listitem>
<para>
initdb defaults to enabling data checksums
<ulink url="&commit_baseurl;04bec894a04">&sect;</ulink>
</para>

<para>
The previous default behavior (checksums disabled) can be obtained using the
new option --no-data-checksums. Note that pg_upgrade will reject upgrading
between clusters with different checksum settings, so if the old cluster does
not have checksums enabled (the previous default), then the new cluster will
need to be initialized with --no-data-checksums in order to allow pg_upgrade
to succeed.
</para>
</listitem>

</itemizedlist>
Expand Down