doc: Document how to run regression tests with custom server settings
Author: Craig Ringer
Discussion:
https://www.postgresql.org/message-id/flat/CAMsr+YF=+ctxbzj3ywmvknujwpxmutuukuv-rgbhgx5i5pl...@mail.gmail.com
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/854
Standardize one aspect of rmgr desc output.
Bring heap and hash rmgr desc output in line with nbtree and GiST desc
output by using the name latestRemovedXid for all fields that output the
contents of the latestRemovedXid field from the WAL record's C struct
(stop using local variants).
This seems
Fix typo in origin.c.
Author: Peter Smith
Discussion:
https://postgr.es/m/CAHut+PsReyuvww_Fn1NN_Vsv0wBP1bnzuhzRFr_2=y1nnzr...@mail.gmail.com
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/cd357c76296e987298e4005b8053adda9e3fb417
Modified Files
--
src/
Fix typo in reorderbuffer.c.
Author: Zhijie Hou
Reviewed-by: Sawada Masahiko
Discussion:
https://postgr.es/m/ba88bb58aaf14284abca16aec04bf279@G08CNEXMBPEKD05.g08.fujitsu.local
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/9da2224ea2bb9801afc29bff6a325bf796868bdc
Replace remaining uses of "whitelist".
Instead describe the action that the list effects, or just use "list"
where the meaning is obvious from context.
Author: Dagfinn Ilmari Mannsåker
Discussion:
https://postgr.es/m/20200615182235.x7lch5n6kcjq4aue%40alap3.anarazel.de
Branch
--
master
Det
pgindent: whitelist/blacklist -> additional/excluded.
Author: Dagfinn Ilmari Mannsåker
Discussion:
https://postgr.es/m/20200615182235.x7lch5n6kcjq4aue%40alap3.anarazel.de
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/fe05b6b620066aec313c43b6b4d6c169d0a346f7
Mod
Rename "enum blacklist" to "uncommitted enums".
We agreed to remove this terminology and use something more descriptive.
Discussion:
https://postgr.es/m/20200615182235.x7lch5n6kcjq4aue%40alap3.anarazel.de
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/c0d4f6d8974
Fix integer-overflow corner cases in substring() functions.
If the substring start index and length overflow when added together,
substring() misbehaved, either throwing a bogus "negative substring
length" error on a case that should succeed, or failing to complain that
a negative length is negati
Fix integer-overflow corner cases in substring() functions.
If the substring start index and length overflow when added together,
substring() misbehaved, either throwing a bogus "negative substring
length" error on a case that should succeed, or failing to complain that
a negative length is negati
Fix integer-overflow corner cases in substring() functions.
If the substring start index and length overflow when added together,
substring() misbehaved, either throwing a bogus "negative substring
length" error on a case that should succeed, or failing to complain that
a negative length is negati
Fix integer-overflow corner cases in substring() functions.
If the substring start index and length overflow when added together,
substring() misbehaved, either throwing a bogus "negative substring
length" error on a case that should succeed, or failing to complain that
a negative length is negati
Remove unused function prototypes.
Cleanup for commit dee663f7.
Reported-by: Tomas Vondra
Discussion:
https://postgr.es/m/CA+hUKGLJ=84yt+nvhkeedauutvhmfq9i-n7k_o50jmq6rpj...@mail.gmail.com
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/87c23d36a3bc81e57b813f13c4
Remove PLPGSQL_DTYPE_ARRAYELEM datum type within pl/pgsql.
In the wake of the previous commit, we don't really need this anymore,
since array assignment is primarily handled by the core code.
The only way that that code could still be reached is that a GET
DIAGNOSTICS target variable could be an
Re-implement pl/pgsql's expression and assignment parsing.
Invent new RawParseModes that allow the core grammar to handle
pl/pgsql expressions and assignments directly, and thereby get rid
of a lot of hackery in pl/pgsql's parser. This moves a good deal
of knowledge about pl/pgsql into the core c
Rethink the "read/write parameter" mechanism in pl/pgsql.
Performance issues with the preceding patch to re-implement array
element assignment within pl/pgsql led me to realize that the read/write
parameter mechanism is misdesigned. Instead of requiring the assignment
source expression to be such
Add the ability for the core grammar to have more than one parse target.
This patch essentially allows gram.y to implement a family of related
syntax trees, rather than necessarily always parsing a list of SQL
statements. raw_parser() gains a new argument, enum RawParseMode,
to say what to do. A
Simplify some comments in xml.c
Author: Justin Pryzby
Discussion: https://postgr.es/m/X/[email protected]
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/b49154b3b7a45523ce4081fdae8d65049342fcec
Modified Files
--
src/backend/utils/adt/xml.c | 1
17 matches
Mail list logo