Hi Vijaykumar
Thank you so much for taking out so much of your time to recreate the bug.
I checked the max_logical_replication_workers on both the nodes and they
are set at 4 at the moment.
The reason why it is failing is that there are 3 existing replications on
the target node already and when
trimming the email, to avoid noise.
I spent a lot of time trying multiple options/combinations and finally
managed to replicate your debug output.
this is when i have ,
postgres=# show max_logical_replication_workers;
* max_logical_replication_workers*
-
* 2*
(1 ro
* *Basic Connectivity from target(subscriber) to source (Publisher)-*
postgres@targethost:~$ psql -h sourcedb-vip --port=5432 --user=dba -d
sourcedb
Password for user dba:
psql (13.3)
Type "help" for help.
sourcedb=#
* *Create Publication*
sourcedb=# CREATE PUBLICATION omx_archive FOR TABLE
sam
On Thu, 3 Feb 2022 at 12:44, Abhishek Bhola
wrote:
> Hi Vijaykumar,
>
> I checked the pg_subscription_rel and all the tables in that subscription
> are in the state - i (initialize).
> I also tried creating a new publication on the source DB with just one
> table and tried to subscribe it, it doe
Hi Vijaykumar,
I checked the pg_subscription_rel and all the tables in that subscription
are in the state - i (initialize).
I also tried creating a new publication on the source DB with just one
table and tried to subscribe it, it doesn't work either.
However, when I try to subscribe it on some ot
On Thu, Feb 3, 2022, 10:32 AM Abhishek Bhola
wrote:
> So far I figured out that the problem is on the subscriber side.
> The same publication, when subscribed to on another DB, works fine.
> Also noticed that the remote_lsn value on the target DB is still 0/0.
>
> targetdb=# select * from pg_repl
So far I figured out that the problem is on the subscriber side.
The same publication, when subscribed to on another DB, works fine.
Also noticed that the remote_lsn value on the target DB is still 0/0.
targetdb=# select * from pg_replication_origin_status ;
local_id | external_id | remote_ls
Update: Tried dropping and recreating publication on the source DB and
subscription still won't move ahead.
Not sure what I am missing.
On Wed, Feb 2, 2022 at 1:20 PM Abhishek Bhola <
abhishek.bh...@japannext.co.jp> wrote:
> The only statement I see on the target DB log is
> "logical replication
The only statement I see on the target DB log is
"logical replication apply worker for subscription ""sub_omx_archive_tci""
has started",""
I don't see the logical replication table synchronization worker started
for any of the tables in this subscription as I see in the other one.
Is the
Hi Abishek,
Have you checked the subscriber and publisher database log files to see if
there is a problem blocking the subscription? For example, a subscribed
table missing a column that exists in the publisher.
Cheers,
Steve
On Wed, Feb 2, 2022 at 1:26 PM Abhishek Bhola <
abhishek.bh...@japann
10 matches
Mail list logo
