pg.ddx.io  pgsql-docs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Boboc Cristi <bobocc@yahoo.com>
To: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
To: Peter Smith <smithpb2250@gmail.com>
Subject: Re: Logical replication missing information
Date: Wed, 23 Nov 2022 09:03:05 +0000 (UTC)
Message-ID: <89363341.1728627.1669194185204@mail.yahoo.com> (raw)
In-Reply-To: <CAHut+Pui7LCgfzkjcqvdcPy+V9G8CRb6X5hL+MB7QqXFBhQMzg@mail.gmail.com>
References: <166870632180.632.14582512493527657072@wrigleys.postgresql.org>
	<CAHut+Pui7LCgfzkjcqvdcPy+V9G8CRb6X5hL+MB7QqXFBhQMzg@mail.gmail.com>

Hello!Thank you very much, the information you just sent to me is very, very valuable!
Best regards, Cristi Boboc 

    On Wednesday, November 23, 2022 at 04:45:09 AM GMT+2, Peter Smith <smithpb2250@gmail.com> wrote:  
 
 On Fri, Nov 18, 2022 at 4:50 AM PG Doc comments form
<noreply@postgresql.org> wrote:
>
> The following documentation comment has been logged on the website:
>
> Page: https://www.postgresql.org/docs/15/logical-replication-row-filter.html
> Description:

Hi,

FYI - I have forwarded this post to the hacker's list, where I think
it will receive more attention.

I am not sure why that (above) page was cited -- the section "31.3 Row
Filters" is specifically about row filtering, whereas the items you
reported seem unrelated to row filters, but are generic for all
Logical Replication.

>
> There are several things missing here and some of them I found to be highly
> important:
> 1. How can I find why a logical replication failed. Currently I only can see
> it "does nothing" in pg_stat_subscriptions.

There should be logs reporting any replication conflicts etc. See [1]
for example logs. See also the answer for #2 below.

> 2. In case of copying the existing data: how can I find which tables or
> partitions were processed and which are on the processing queue (while
> monitoring I have observed no specific order or rule).

There is no predictable processing queue or order - The initial
tablesyncs might be happening in multiple asynchronous processes
according to the GUC max_sync_workers_per_subscription [2].

Below I show examples of replicating two tables (tab1 and tab2).

~~

view thread (3+ messages)

Message-ID: <89363341.1728627.1669194185204@mail.yahoo.com>
Permalink:  ../89363341.1728627.1669194185204@mail.yahoo.com/
Also on:    postgresql.org/message-id/89363341.1728627.1669194185204@mail.yahoo.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-docs@postgresql.org
  Cc: bobocc@yahoo.com, pgsql-hackers@lists.postgresql.org, smithpb2250@gmail.com
  Subject: Re: Logical replication missing information
  In-Reply-To: <89363341.1728627.1669194185204@mail.yahoo.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox