Fix incorrect format placeholders
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/bb1412baa5b57652ef69f7e995657d085fd308e4
Modified Files
--
src/backend/libpq/auth-sasl.c | 2 +-
src/backend/libpq/auth-scram.c | 2 +-
src/backend/libpq/auth.c | 4 ++
Invalidate relcache for publications defined for all tables.
Updates/Deletes on a relation were allowed even without replica identity
after we define the publication for all tables. This would later lead to
an error on subscribers. The reason was that for such publications we were
not invalidating
Invalidate relcache for publications defined for all tables.
Updates/Deletes on a relation were allowed even without replica identity
after we define the publication for all tables. This would later lead to
an error on subscribers. The reason was that for such publications we were
not invalidating
Invalidate relcache for publications defined for all tables.
Updates/Deletes on a relation were allowed even without replica identity
after we define the publication for all tables. This would later lead to
an error on subscribers. The reason was that for such publications we were
not invalidating
Invalidate relcache for publications defined for all tables.
Updates/Deletes on a relation were allowed even without replica identity
after we define the publication for all tables. This would later lead to
an error on subscribers. The reason was that for such publications we were
not invalidating
Invalidate relcache for publications defined for all tables.
Updates/Deletes on a relation were allowed even without replica identity
after we define the publication for all tables. This would later lead to
an error on subscribers. The reason was that for such publications we were
not invalidating
Invalidate relcache for publications defined for all tables.
Updates/Deletes on a relation were allowed even without replica identity
after we define the publication for all tables. This would later lead to
an error on subscribers. The reason was that for such publications we were
not invalidating
Fix compilation warning in ipci.c
A Size had better use %zu when printed.
Oversight in bd17880, per buildfarm member lapwing.
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/aa37a439db6bd328d68ce815ab9e12467f42493b
Modified Files
--
src/backend/storage
Introduce GUC shared_memory_size
This runtime-computed GUC shows the size of the server's main shared
memory area, taking into account the amount of shared memory allocated
by extensions as this is calculated after processing
shared_preload_libraries.
Author: Nathan Bossart
Discussion: https://po
Clean up some code using "(expr) ? true : false"
All the code paths simplified here were already using a boolean or used
an expression that led to zero or one, making the extra bits
unnecessary.
Author: Justin Pryzby
Reviewed-by: Tom Lane, Michael Paquier, Peter Smith
Discussion: https://postgr.e
Consistently use read-only instead of "read only"
This affects one message and some documentation that used the format
"read only", unlike everything else that used read-only.
Backpatch-through: 14
Discussion:
https://postgr.es/m/cabuevexuxkwn0ym3+wdseqsvk6crrj-hewocgvx3r4-xvx4...@mail.gmail.com
Consistently use read-only instead of "read only"
This affects one message and some documentation that used the format
"read only", unlike everything else that used read-only.
Backpatch-through: 14
Discussion:
https://postgr.es/m/cabuevexuxkwn0ym3+wdseqsvk6crrj-hewocgvx3r4-xvx4...@mail.gmail.com
windows: Only consider us to be running as service if stderr is invalid.
Previously pgwin32_is_service() would falsely return true when postgres is
started from somewhere within a service, but not as a service. That is
e.g. always the case with windows docker containers, which some CI services
use
Finish reverting 3eda9fc09fd6b9a1aec2d0113c633c69c3214b4d.
Commit 67c33a114 should have set v14's catversion back to what it was
before 3eda9fc09, to avoid forcing a useless pg_upgrade cycle on users
of 14beta3. Do that now.
Discussion: https://postgr.es/m/[email protected]
Branc
On 06/09/2021 11:50, Amit Langote wrote:
Quite late but to I was looking at this and noticed this comment:
+ /*
+* Direct modifications cannot be re-evaluated by EvalPlanQual, so
+* don't bother preparing the FDW. There can ForeignScan nodes in the
+* EvalPlanQual
Fix missing words in comment.
Introduced by commit c3928b467a, backpatch to v14 like that one.
Author: Amit Langote
Discussion:
https://www.postgresql.org/message-id/CA+HiwqFQgNLS6VGntMcuJV6erBFV425xA6wBVnY=41gk4zc...@mail.gmail.com
Branch
--
REL_14_STABLE
Details
---
https://git.postg
Fix missing words in comment.
Introduced by commit c3928b467a, backpatch to v14 like that one.
Author: Amit Langote
Discussion:
https://www.postgresql.org/message-id/CA+HiwqFQgNLS6VGntMcuJV6erBFV425xA6wBVnY=41gk4zc...@mail.gmail.com
Branch
--
master
Details
---
https://git.postgresql.o
17 matches
Mail list logo
