<!--
Version 18 contains a number of changes that may affect compatibility with previous releases. Observe the following incompatibilities:

Pas un souci / changement évoqué ou à évoquer

    Change initdb default to enable data checksums (Greg Sabino Mullane) §

    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.

    Change time zone abbreviation handling (Tom Lane) §

    The system will now favor the current session's time zone abbreviations before checking the server variable timezone_abbreviations. Previously timezone_abbreviations was checked first.

    Change full text search to use the default collation provider of the cluster to read configuration files and dictionaries, rather than always using libc (Peter Eisentraut) §

    
    Change VACUUM and ANALYZE to process the inheritance children of a parent (Michael Harris) § -> changement
    The previous behavior can be performed by using the new ONLY option.

    Disallow unlogged partitioned tables (Michael Paquier) §

Warning innocent :

    Deprecate MD5 password authentication (Nathan Bossart) §

    Support for MD5 passwords will be removed in a future major version release. CREATE ROLE and ALTER ROLE now emit deprecation warnings when setting MD5 passwords. These warnings can be disabled by setting the md5_password_warnings parameter to off.

    
En fait des fix :    

    Prevent COPY FROM from treating \. as an end-of-file marker when reading CSV files (Daniel Vérité, Tom Lane) § §

    psql will still treat \. as an end-of-file marker when reading CSV files from STDIN. Older psql clients connecting to PostgreSQL 18 servers might experience \copy problems. This release also enforces that \. must appear alone on a line.

    Previously ALTER TABLE SET [UN]LOGGED did nothing, and the creation of an unlogged partitioned table did not cause its children to be unlogged.

Cas vraiment tordus/rarissimes

    Execute AFTER triggers as the role that was active when trigger events were queued (Laurenz Albe) §
    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.

    Remove non-functional support for rule privileges in GRANT/REVOKE (Fujii Masao) §
    These have been non-functional since PostgreSQL 8.2.

    Remove column pg_backend_memory_contexts.parent (Melih Mutlu) §
    This is no longer needed since pg_backend_memory_contexts.path was added.

    Change pg_backend_memory_contexts.level and pg_log_backend_memory_contexts() to be one-based (Melih Mutlu, Atsushi Torikoshi, David Rowley, Fujii Masao) § § §
    These were previously zero-based.

    Clusters that default to non-libc collation providers (e.g., ICU, builtin) that behave differently than libc for characters processed by LC_CTYPE could observe changes in behavior of some full-text search functions, as well as the pg_trgm extension. When upgrading such clusters using pg_upgrade, it is recommended to reindex all indexes related to full-text search and pg_trgm after the upgrade.


-->


<div class="slide-content">

</div>

<div class="notes">

</div>


