Make formatting in nls.mk files more consistent
Some of the nls.mk files used different indentation or line breaks
than the majority, which makes editing these files unnecessarily
confusing.
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/2e810bdb7f0a32329a7f3868fae
Fix pg_sequence_last_value() for unlogged sequences on standbys.
Presently, when this function is called for an unlogged sequence on
a standby server, it will error out with a message like
ERROR: could not open file "base/5/16388": No such file or directory
Since the pg_sequences system
Fix pg_sequence_last_value() for unlogged sequences on standbys.
Presently, when this function is called for an unlogged sequence on
a standby server, it will error out with a message like
ERROR: could not open file "base/5/16388": No such file or directory
Since the pg_sequences system
Fix pg_sequence_last_value() for unlogged sequences on standbys.
Presently, when this function is called for an unlogged sequence on
a standby server, it will error out with a message like
ERROR: could not open file "base/5/16388": No such file or directory
Since the pg_sequences system
Fix pg_sequence_last_value() for unlogged sequences on standbys.
Presently, when this function is called for an unlogged sequence on
a standby server, it will error out with a message like
ERROR: could not open file "base/5/16388": No such file or directory
Since the pg_sequences system
Fix pg_sequence_last_value() for unlogged sequences on standbys.
Presently, when this function is called for an unlogged sequence on
a standby server, it will error out with a message like
ERROR: could not open file "base/5/16388": No such file or directory
Since the pg_sequences system
Fix pg_sequence_last_value() for unlogged sequences on standbys.
Presently, when this function is called for an unlogged sequence on
a standby server, it will error out with a message like
ERROR: could not open file "base/5/16388": No such file or directory
Since the pg_sequences system
Add missing gettext triggers
Due to commit dc212340058, which added use of
src/common/parse_manifest.c in the backend.
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/ab4d7a38c36dba3997e9b585448837ccf6384aed
Modified Files
--
src/backend/nls.mk | 7
Fix memory leaks in error reporting with LOG level
When loglevel is set to LOG, allocated strings used in the error
message would leak. Fix by explicitly pfreeing them.
Author: Ranier Vilela
Reviewed-by: Daniel Gustafsson
Reviewed-by: Michael Paquier
Discussion:
https://postgr.es/m/caeudqaqme
Remove auth-options support from initdb
When --auth was added to initdb in commit e7029b212755 it had support
for auth options separated by space from the auth type, like:
--auth pam
--auth ident sameuser
Passing an option to the ident auth type was removed in 01c1a12a5bb4
which left th
Add missing source files to pg_combinebackup/nls.mk
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/9eb54a258f53dd1d7f198e74c1b11b516ad2e98a
Modified Files
--
src/bin/pg_combinebackup/nls.mk | 12 +---
1 file changed, 9 insertions(+), 3 deletions(
Add missing gettext triggers
Commit d6607016c7 moved all the jsonapi.c error messages into
token_error(). This needs to be added to the various nls.mk files
that use this. Since that makes token_error() effectively a globally
known symbol, the name seems a bit too general, so rename to
json_toke
Pre-beta mechanical code beautification.
Run pgindent, pgperltidy, and reformat-dat-files.
The pgindent part of this is pretty small, consisting mainly of
fixing up self-inflicted formatting damage from patches that
hadn't bothered to add their new typedefs to typedefs.list.
In order to keep it f
Add da256a4a7 to .git-blame-ignore-revs.
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/ce13f54e6055d24e21cc969f498f121c37616921
Modified Files
--
.git-blame-ignore-revs | 3 +++
1 file changed, 3 insertions(+)
Do pre-release housekeeping on catalog data.
Run renumber_oids.pl to move high-numbered OIDs down, as per pre-beta
tasks specified by RELEASE_CHANGES. For reference, the command was
./renumber_oids.pl --first-mapped-oid 8000 --target-oid 6300
Branch
--
master
Details
---
https://git.po
Fix handling of polymorphic output arguments for procedures.
Most of the infrastructure for procedure arguments was already
okay with polymorphic output arguments, but it turns out that
CallStmtResultDesc() was a few bricks shy of a load here. It thought
all it needed to do was call build_functio
Fix handling of polymorphic output arguments for procedures.
Most of the infrastructure for procedure arguments was already
okay with polymorphic output arguments, but it turns out that
CallStmtResultDesc() was a few bricks shy of a load here. It thought
all it needed to do was call build_functio
Fix handling of polymorphic output arguments for procedures.
Most of the infrastructure for procedure arguments was already
okay with polymorphic output arguments, but it turns out that
CallStmtResultDesc() was a few bricks shy of a load here. It thought
all it needed to do was call build_functio
Fix handling of polymorphic output arguments for procedures.
Most of the infrastructure for procedure arguments was already
okay with polymorphic output arguments, but it turns out that
CallStmtResultDesc() was a few bricks shy of a load here. It thought
all it needed to do was call build_functio
Fix handling of polymorphic output arguments for procedures.
Most of the infrastructure for procedure arguments was already
okay with polymorphic output arguments, but it turns out that
CallStmtResultDesc() was a few bricks shy of a load here. It thought
all it needed to do was call build_functio
Fix handling of polymorphic output arguments for procedures.
Most of the infrastructure for procedure arguments was already
okay with polymorphic output arguments, but it turns out that
CallStmtResultDesc() was a few bricks shy of a load here. It thought
all it needed to do was call build_functio
doc PG 17 relnotes: add two optimizer items
One is about subqueries becoming joins and the other is about optimizing
LIMIT by improving startup cost.
Reported-by: Andy Fan
Discussion: https://postgr.es/m/87h6f4ncc6@163.com
Reviewed-by: David Rowley
Backpatch-through: master
Branch
--
doc PG 17 relnotes: wording fixes
Reported-by: Elena Indrupskaya
Discussion:
https://postgr.es/m/22110133-bca5-4a99-889c-aa0096423...@postgrespro.ru
Author: Elena Indrupskaya
Backpatch-through: master
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/78e4841c1bbc
doc PG 17 relnotes: wording fix
Reported-by: Pantelis Theodosiou
Discussion:
https://postgr.es/m/CAE3TBxxvkSGJGv7S0SMLSAe0khrQJBHsTca799r=vdjtn+b...@mail.gmail.com
Backpatch-through: master
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/2b065fc549ed60249f211a7f
doc PG 17 relnotes: remove NOT NULL revert, add ALPN item
Make current as of 2024-05-14
Backpatch-through: master
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/9bb47338d070105916157528304b79a0ad7baa81
Modified Files
--
doc/src/sgml/release-17.sgml |
doc PG 17 relnotes: add logical replication apply subtrans item
Reported-by: Masahiko Sawada
Discussion:
https://postgr.es/m/CAD21AoD5jjB+M+BK5JTis8=W1g8KsS1961FyMqRpj=nbfxr...@mail.gmail.com
Backpatch-through: master
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitd
Fix incorrect year in some copyright notices added this year
A few patches that were written <= 2023 and committed in 2024 still
contained 2023 copyright year. Fix that.
Discussion:
https://postgr.es/m/caaphdvr5egyw3fmhbag-uq2p_aizwco1zjs6vbq18kqn64-...@mail.gmail.com
Branch
--
master
Det
Add missing newline at the end of index_including.sql
Thinko in a63224be49b8.
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/54b69f1bd730a228a666441592a12d2a0cbe2a06
Modified Files
--
src/test/regress/sql/index_including.sql | 2 +-
1 file changed, 1 in
28 matches
Mail list logo
