Fix the test case introduced by commit 8756930190.
Before dropping a relation, ensure that it has reached a 'ready' state
after initial synchronization.
Author: Vignesh C
Reviewed-By: Amit Kapila
Discussion:
Raise a warning if there is a possibility of data from multiple origins.
This commit raises a warning message for a combination of options
('copy_data = true' and 'origin = none') during CREATE/ALTER subscription
operations if the publication tables were also replicated from other
publishers.
Message style fixes
Branch
--
REL_15_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/144cefac92644f338c35b77f6d9b4a9456c80563
Modified Files
--
src/backend/replication/logical/worker.c | 6 +++---
src/backend/utils/init/postinit.c| 7 ---
Message style fixes
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/4b4663fb4a704b7a145ed6ec018b1f0c116eeb6b
Modified Files
--
src/backend/replication/logical/worker.c | 6 +++---
src/backend/utils/init/postinit.c| 7 ---
Make MemoryContextContains work correctly again
c6e0fe1f2 recently changed the way we store headers for allocated chunks
of memory. Prior to that commit, we stored a pointer to the owning
MemoryContext directly prior to the pointer to the allocated memory.
That's no longer true and c6e0fe1f2
Tag refs/tags/REL_15_BETA4 was created.
On Wed, Sep 07, 2022 at 11:11:37AM +0200, Peter Eisentraut wrote:
> On 06.09.22 08:27, Michael Paquier wrote:
> > On Tue, Sep 06, 2022 at 01:57:53AM -0400, Tom Lane wrote:
> > > Peter Eisentraut writes:
> > > > I think renumbering this makes sense. We could just leave the comment
> > > > as is
Renumber confusing value for GUC_UNIT_BYTE
It had a power-of-two value, which looks right, and causes the other
values which aren't powers-of-two to look wrong. But this is tested
for equality and not a bitwise test.
See also:
6e7baa322773ff8c79d4d8883c99fdeff5bfa679
