Fix NLS for incorrect GUC enum value hint message
The translation markers were applied at the wrong place, so no string
was extracted for translation.
Also add translator comments here and in a similar place.
Reviewed-by: Álvaro Herrera
Discussion:
https://www.postgresql.org/message-id/2c961fa
Add to c.h
This allows using the C11 constructs alignas and alignof (not done in
this patch).
Reviewed-by: Chao Li
Discussion:
https://www.postgresql.org/message-id/flat/46f05236-d4d4-4b4e-84d4-faa500f14691%40eisentraut.org
Branch
--
master
Details
---
https://git.postgresql.org/pg/c
Fix typo in nodeHash.c
Replace "overlow" with "overflow".
Author: Tender Wang
Discussion:
https://postgr.es/m/cahewxnnzfjajyltkp78he2pq17mjbqfdqqg+0x6wo7ymub6...@mail.gmail.com
Branch
--
REL_18_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/db0d2d75d0bbdf08e2756b075d4a887
Fix typo in nodeHash.c
Replace "overlow" with "overflow".
Author: Tender Wang
Discussion:
https://postgr.es/m/cahewxnnzfjajyltkp78he2pq17mjbqfdqqg+0x6wo7ymub6...@mail.gmail.com
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/4d3f623ea887a7b6e74d7567e3e0c4b66fd58e
Fix pg_popcount_aarch64.c to build with ancient glibc releases.
Like commit 6d969ca68, except here we are mopping up after 519338ace.
(There are no other uses of in the tree, so we should
be done now.)
Reported-by: GaoZengqi
Author: Tom Lane
Discussion:
https://postgr.es/m/cafmbtr3av62-jbzdhf
Fix pg_popcount_aarch64.c to build with ancient glibc releases.
Like commit 6d969ca68, except here we are mopping up after 519338ace.
(There are no other uses of in the tree, so we should
be done now.)
Reported-by: GaoZengqi
Author: Tom Lane
Discussion:
https://postgr.es/m/cafmbtr3av62-jbzdhf
Fix typo
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/77fb3959a45d1a748cb28f3f58da18c6645b45d3
Modified Files
--
src/backend/executor/nodeHash.c | 2 +-
src/bin/pg_dump/t/005_pg_dump_filterfile.pl | 2 +-
src/interfaces/libpq/fe-secure-opens
Fix typo
Branch
--
REL_18_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/b1fbc6494ef57964adb22f0ee14ec314010b5629
Modified Files
--
src/backend/executor/nodeHash.c | 2 +-
src/bin/pg_dump/t/005_pg_dump_filterfile.pl | 2 +-
src/interfaces/libpq/fe-secur
Don't allow CTEs to determine semantic levels of aggregates.
The fix for bug #19055 (commit b0cc0a71e) allowed CTE references in
sub-selects within aggregate functions to affect the semantic levels
assigned to such aggregates. It turns out this broke some related
cases, leading to assertion failu
Don't allow CTEs to determine semantic levels of aggregates.
The fix for bug #19055 (commit b0cc0a71e) allowed CTE references in
sub-selects within aggregate functions to affect the semantic levels
assigned to such aggregates. It turns out this broke some related
cases, leading to assertion failu
Don't allow CTEs to determine semantic levels of aggregates.
The fix for bug #19055 (commit b0cc0a71e) allowed CTE references in
sub-selects within aggregate functions to affect the semantic levels
assigned to such aggregates. It turns out this broke some related
cases, leading to assertion failu
Don't allow CTEs to determine semantic levels of aggregates.
The fix for bug #19055 (commit b0cc0a71e) allowed CTE references in
sub-selects within aggregate functions to affect the semantic levels
assigned to such aggregates. It turns out this broke some related
cases, leading to assertion failu
Don't allow CTEs to determine semantic levels of aggregates.
The fix for bug #19055 (commit b0cc0a71e) allowed CTE references in
sub-selects within aggregate functions to affect the semantic levels
assigned to such aggregates. It turns out this broke some related
cases, leading to assertion failu
Don't allow CTEs to determine semantic levels of aggregates.
The fix for bug #19055 (commit b0cc0a71e) allowed CTE references in
sub-selects within aggregate functions to affect the semantic levels
assigned to such aggregates. It turns out this broke some related
cases, leading to assertion failu
Add commit f63ae72bbc to .git-blame-ignore-revs.
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/faf4128ad36425045c1ffb48537d094253bba0ef
Modified Files
--
.git-blame-ignore-revs | 3 +++
1 file changed, 3 insertions(+)
Switch from tabs to spaces in postgresql.conf.sample.
This file is written for 8-space tabs, since we expect that most
users who edit their configuration files use 8-space tabs.
However, most of PostgreSQL is written for 4-space tabs, and at
least one popular web interface defaults to 4-space tabs
Update .editorconfig and .gitattributes for postgresql.conf.sample.
This commit updates .editorconfig and .gitattributes in preparation
for a follow-up commit that will modify this file to use spaces
instead of tabs.
Reviewed-by: Tom Lane
Reviewed-by: Chao Li
Discussion: https://postgr.es/m/aRe
Check for tabs in postgresql.conf.sample.
The previous commit updated this file to use spaces instead of
tabs. This commit adds a test to ensure that no new tabs are
added.
Reviewed-by: Tom Lane
Reviewed-by: Chao Li
Discussion: https://postgr.es/m/aReNUKdMgKxLqmq7%40nathan
Branch
--
maste
Log a note at program start when running in dry-run mode
Users might get some peace of mind knowing their data is not being
destroyed or whatever.
Author: Peter Smith
Reviewed-by: Álvaro Herrera
Discussion:
https://postgr.es/m/cahut+psvqjqnqo0kt0s2oegenkvj8fuuy-qs5syyqmt24r2...@mail.gmail.com
19 matches
Mail list logo
