postgresql.git/doc, branch REL_18_STABLE

doc: Database and tablespace size functions throws error

2026-09-15T11:46:52Z

Commit b6463ea6ef3e46 added an explicit ereport on missing object to pg_database_size and pg_tablespace_size, but the documentation wasn't updated to match. Author: Zhong ShiHao Reviewed-by: Chao Li Reviewed-by: solai v Discussion: https://postgr.es/m/CAGRkXqQSegqDnkRf344G=80mJMn78o9u=auHnx=u1jf=XpuE0A@mail.gmail.com Backpatch-through: 18

doc: Fix output column name for pg_stat_get_backend_subxact()

2026-09-12T00:04:08Z

pg_stat_get_backend_subxact()'s second attribute was written as "subxact_overflow" in the docs, but its name is "subxact_overflowed". Note that the attribute name is still wrong in the TupleDesc generated in the function; pg_proc agrees with "overflowed". Author: Shihao Zhong Reviewed-by: Jim Jones Reviewed-by: Michael Paquier Discussion: https://postgr.es/m/CAGRkXqTBZ+zbVuDC8xGEB6Btj61hsui5H5nGqzFBDyOXc=4bjQ@mail.gmail.com Backpatch-through: 16

doc: clarify aliasing of VALUES in FROM clauses

2026-09-01T13:48:30Z

The VALUES reference page said that an AS clause was required when VALUES is used in a FROM clause. This was imprecise because AS is optional when specifying an alias. In v14 and v15, a table alias is still required in this case, so state that explicitly instead. In v16 and later, commit bcedd8f5fce made table aliases for subqueries in FROM clauses optional, so state that the table alias is optional there. In all branches, continue to recommend explicit column aliases as good practice. Backpatch to all supported versions. Author: Ian Barwick Reviewed-by: Laurenz Albe Reviewed-by: Fujii Masao Discussion: https://postgr.es/m/CAB8KJ=jrvZdNLLhYSiCgbjLTz2LKEjYw+-HVQkaF+kgk61KtHA@mail.gmail.com Backpatch-through: 14

Doc: fix typo

2026-08-22T00:49:42Z

Author: Jochen Bandhauer Discussion: https://postgr.es/m/69ecfa04-9177-42fd-8d5d-9f375669fc5b@jbitc.de Backpatch-through: 14

doc: Fix description of log_line_prefix %L in release notes

2026-08-18T06:33:02Z

%L was described as showing in output the client IP, but it shows the local IP of the server connected to. Author: Keisuke Kuroda Reviewed-by: Greg Sabino Mullane Discussion: https://postgr.es/m/CANDwggK8AZJx+tGKY+h_8a90rqZ_+4dvGOFvDuRVVSjQvAafbg@mail.gmail.com Backpatch-through: 18, only

Doc: clean up documentation about text search datatype limits.

2026-08-17T22:17:51Z

textsearch.sgml neglected to mention that the MAXSTRPOS total-length limit applies to tsquery as well as tsvector. It also claims that there is a 32K limit on the total number of nodes in a tsquery, which is wrong. (I suspect that QueryOperator.left may once have been int16, which would give rise to such a limit. But it's uint32 now, so you'd hit the 1GB varlena limit well before overflowing that.) While at it, re-order the bullet points into an order that makes more sense, to me anyway. Reported-by: Claude Code (via Noah Misch) Author: Tom Lane Reviewed-by: Chao Li Discussion: https://postgr.es/m/455079.1786897319@sss.pgh.pa.us Backpatch-through: 14

doc: Clarify the logging collector's guarantees.

2026-08-14T20:27:16Z

Presently, the documentation for logging_collector says that the collector "is designed to never lose messages," which reads as a stronger promise than we actually make. The collector does not fsync the log file or retry failed writes, so log messages can go missing after an operating system crash, power loss, or a write error. Reword that sentence and add a note about what is not guaranteed. Author: Daniel Bauman Reviewed-by: Fujii Masao Reviewed-by: Zhenwei Shang Reviewed-by: Robert Treat Discussion: https://postgr.es/m/CAMtj0_a86DdDKkW-ReVpQpqjndVS6GMrwXVpQY4G3-SGY7saMQ%40mail.gmail.com Backpatch-through: 14

Release notes for 18.6.

2026-08-11T18:37:01Z

Farewell, 18.5; we hardly knew ye.

Last-minute updates for release notes.

2026-08-10T16:15:10Z

Security: CVE-2026-6464, CVE-2026-6469, CVE-2026-6470, CVE-2026-6471, CVE-2026-14662, CVE-2026-14663, CVE-2026-14664, CVE-2026-14666, CVE-2026-14668, CVE-2026-14669, CVE-2026-14670, CVE-2026-14671, CVE-2026-14672, CVE-2026-14673, CVE-2026-14676, CVE-2026-14677, CVE-2026-14678, CVE-2026-14679, CVE-2026-14680, CVE-2026-14681, CVE-2026-15741, CVE-2026-15742, CVE-2026-16238, CVE-2026-16239, CVE-2026-16241, CVE-2026-18024, CVE-2026-18408, CVE-2026-19385

psql: Don't do backquote expansion in \unrestrict.

2026-08-10T13:38:13Z

This oversight in commit 71ea0d6795 allows a malicious server to inject shell commands into plain-text dump output that are run at restore time on the machine running psql. To fix, interpret all text after \unrestrict until the end of the line as its argument. Reported-by: Lucas Velgus Reported-by: Filip Janus Reported-by: Daniel Bakker Author: Nathan Bossart Reviewed-by: Robert Haas Reviewed-by: Noah Misch Security: CVE-2026-18408 Backpatch-through: 14