pgsql: doc: first draft of Postgres 17 release notes

doc: first draft of Postgres 17 release notes Backpatch-through: master Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/e305f71565e203e08e47d7094082188f5737317f Modified Files -- doc/src/sgml/release-17.sgml | 2825 +

pgsql: Fix overread in JSON parsing errors for incomplete byte sequence

Fix overread in JSON parsing errors for incomplete byte sequences json_lex_string() relies on pg_encoding_mblen_bounded() to point to the end of a JSON string when generating an error message, and the input it uses is not guaranteed to be null-terminated. It was possible to walk off the end of th

pgsql: Fix overread in JSON parsing errors for incomplete byte sequence

Fix overread in JSON parsing errors for incomplete byte sequences json_lex_string() relies on pg_encoding_mblen_bounded() to point to the end of a JSON string when generating an error message, and the input it uses is not guaranteed to be null-terminated. It was possible to walk off the end of th

pgsql: Fix overread in JSON parsing errors for incomplete byte sequence

Fix overread in JSON parsing errors for incomplete byte sequences json_lex_string() relies on pg_encoding_mblen_bounded() to point to the end of a JSON string when generating an error message, and the input it uses is not guaranteed to be null-terminated. It was possible to walk off the end of th

pgsql: Fix overread in JSON parsing errors for incomplete byte sequence

Fix overread in JSON parsing errors for incomplete byte sequences json_lex_string() relies on pg_encoding_mblen_bounded() to point to the end of a JSON string when generating an error message, and the input it uses is not guaranteed to be null-terminated. It was possible to walk off the end of th

pgsql: Fix overread in JSON parsing errors for incomplete byte sequence

Fix overread in JSON parsing errors for incomplete byte sequences json_lex_string() relies on pg_encoding_mblen_bounded() to point to the end of a JSON string when generating an error message, and the input it uses is not guaranteed to be null-terminated. It was possible to walk off the end of th

Re: pgsql: Add allow_alter_system GUC.

On Fri, Mar 29, 2024 at 08:47:18AM -0400, Robert Haas wrote: > Oh no! Jelte, I'm so sorry ... I spelled your name wrong in this > commit message. :-( > > Please accept my apologies. I have corrected his name in the release notes for this item. -- Bruce Momjian https://momjian.us ED

pgsql: Doc: document that triggers can break referential integrity.

Doc: document that triggers can break referential integrity. User-written triggers can modify or block the effects of SQL update and delete operations. That includes operations that are executed to implement foreign keys' referential integrity actions (such as ON UPDATE SET NULL or ON DELETE CASC

pgsql: Add test for REPLICA IDENTITY with a temporal key

Add test for REPLICA IDENTITY with a temporal key You can only use REPLICA IDENTITY USING INDEX with a unique B-tree index. This commit just adds a test showing that you cannot use it with a WITHOUT OVERLAPS index (which is GiST). Author: Paul A. Jungwirth Discussion: https://www.postgresql.or

pgsql: doc: Improve order of options on pg_upgrade reference page

doc: Improve order of options on pg_upgrade reference page Put the new long-only options in a location that is consistent with the existing long-only options and also the --help output. Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/84f08f2215754cd03feaa82bbdf10fc1

pgsql: Fix typo in src/backend/utils/resowner/README.

Fix typo in src/backend/utils/resowner/README. Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/4364e0126ec7663363cf2dff86a0f6da949fc002 Modified Files -- src/backend/utils/resowner/README | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)