At Thu, 4 Aug 2022 10:56:45 +0200, Marco Slot wrote in
> On Wed, Aug 11, 2021 at 1:37 PM Amit Kapila wrote:
> > I think it is and the context is generated via
> > output_plugin_error_callback. Is this reproducible for you and if so,
> > can you share a test case or some steps to reproduce this?
On Wed, Aug 11, 2021 at 1:37 PM Amit Kapila wrote:
> I think it is and the context is generated via
> output_plugin_error_callback. Is this reproducible for you and if so,
> can you share a test case or some steps to reproduce this? Does this
> work and suddenly start giving errors or it happens t
On Wed, 11 Aug 2021 at 07:37, Amit Kapila wrote:
> On Wed, Aug 11, 2021 at 4:57 PM Dave Cramer wrote:
> >
> > On Wed, 11 Aug 2021 at 07:24, Amit Kapila
> wrote:
> >>
> >> On Wed, Aug 11, 2021 at 1:18 AM Dave Cramer
> wrote:
> >> >
> >> > Reviving this thread
> >> >
> >> > 2021-08-10 19:05:09.0
On Wed, Aug 11, 2021 at 4:57 PM Dave Cramer wrote:
>
> On Wed, 11 Aug 2021 at 07:24, Amit Kapila wrote:
>>
>> On Wed, Aug 11, 2021 at 1:18 AM Dave Cramer wrote:
>> >
>> > Reviving this thread
>> >
>> > 2021-08-10 19:05:09.096 UTC [3738] LOG: logical replication apply worker
>> > for subscripti
On Wed, 11 Aug 2021 at 07:24, Amit Kapila wrote:
> On Wed, Aug 11, 2021 at 1:18 AM Dave Cramer wrote:
> >
> > Reviving this thread
> >
> > 2021-08-10 19:05:09.096 UTC [3738] LOG: logical replication apply
> worker for subscription "sub_mycluster_alltables" has started
> > 2021-08-10 19:05:09.10
On Wed, Aug 11, 2021 at 1:18 AM Dave Cramer wrote:
>
> Reviving this thread
>
> 2021-08-10 19:05:09.096 UTC [3738] LOG: logical replication apply worker for
> subscription "sub_mycluster_alltables" has started
> 2021-08-10 19:05:09.107 UTC [3739] LOG: logical replication table
> synchronizatio
Reviving this thread
2021-08-10 19:05:09.096 UTC [3738] LOG: logical replication apply
worker for subscription "sub_mycluster_alltables" has started
2021-08-10 19:05:09.107 UTC [3739] LOG: logical replication table
synchronization worker for subscription "sub_mycluster_alltables",
table "t_rando
> 20 дек. 2019 г., в 06:39, Tomas Vondra
> написал(а):
>
> While trying to reproduce this I however ran into a related issue with
> pgoutput/pg_logical_slot_get_binary_changes. If you call the function
> repeatedly (~10x) you'll get an error like this:
>
> FATAL: out of relcache_callback_lis
I've been running into a similar issue and am a little puzzled by it,
especially since it survives restarts.
On Fri, Dec 20, 2019 at 2:39 AM Tomas Vondra
wrote:
> Yeah, I don't see this error message anywhere in our sources on 11 or
> 12, so perhaps debezium does something funny? It's not clear t
On 12/24/20 12:50 PM, Marco Slot wrote:
I've been running into a similar issue and am a little puzzled by it,
especially since it survives restarts.
Interesting. Which PostgreSQL version are you using? Any idea how to
reproduce it? Were there any failures right before the issue appeared?
I
On Thu, 19 Dec 2019 19:19:56 +0100
Peter Eisentraut wrote:
> On 2019-12-19 19:15, Dave Cramer wrote:
> > It seems that if you drop the publication on an existing slot it needs
> > to be recreated. Is this expected behaviour
>
> A publication is not associated with a slot. Only a subscription
On Thu, Dec 19, 2019 at 07:19:56PM +0100, Peter Eisentraut wrote:
On 2019-12-19 19:15, Dave Cramer wrote:
It seems that if you drop the publication on an existing slot it
needs to be recreated. Is this expected behaviour
A publication is not associated with a slot. Only a subscription is
ass
On 2019-12-19 19:15, Dave Cramer wrote:
It seems that if you drop the publication on an existing slot it needs
to be recreated. Is this expected behaviour
A publication is not associated with a slot. Only a subscription is
associated with a slot.
drop publication dbz_publication ;
DROP PUB
On Thu, 19 Dec 2019 at 11:59, Dave Cramer wrote:
> The publication exists but for some reason the function can't find it
>
> SELECT * FROM pg_logical_slot_get_binary_changes('debezium', NULL,
> NULL,'proto_version','1','publication_names','dbz_publication');
> ERROR: publication "dbz_publication
The publication exists but for some reason the function can't find it
SELECT * FROM pg_logical_slot_get_binary_changes('debezium', NULL,
NULL,'proto_version','1','publication_names','dbz_publication');
ERROR: publication "dbz_publication" does not exist
CONTEXT: slot "debezium", output plugin "p
15 matches
Mail list logo
