pg.ddx.io pgsql-docs@postgresql.org mailing list archive
help / color / mirror / Atom feedLogical replication missing information
3+ messages / 3 participants
[nested] [flat]
* Logical replication missing information
@ 2022-11-17 17:32 PG Doc comments form <noreply@postgresql.org>
0 siblings, 1 reply; 3+ messages in thread
From: PG Doc comments form @ 2022-11-17 17:32 UTC (permalink / raw)
To: pgsql-docs@lists.postgresql.org; +Cc: bobocc@yahoo.com
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/15/logical-replication-row-filter.html
Description:
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.
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).
3. In case of copying the existing data there is no option to update the row
based on the Primary Key if it already exists at the destination. The COPY
only fails.
4. Is it possible to restart an interrupted logical replication. If yes,
then how? Taking in account the already existing data!!!
IMHO there are some big functionality features still missing, but they can
be added.
Thank you!
^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: Logical replication missing information
@ 2022-11-23 02:44 Peter Smith <smithpb2250@gmail.com>
parent: PG Doc comments form <noreply@postgresql.org>
0 siblings, 1 reply; 3+ messages in thread
From: Peter Smith @ 2022-11-23 02:44 UTC (permalink / raw)
To: bobocc@yahoo.com, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
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).
~~
^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: Logical replication missing information
@ 2022-11-23 09:03 Boboc Cristi <bobocc@yahoo.com>
parent: Peter Smith <smithpb2250@gmail.com>
0 siblings, 0 replies; 3+ messages in thread
From: Boboc Cristi @ 2022-11-23 09:03 UTC (permalink / raw)
To: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>; Peter Smith <smithpb2250@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).
~~
^ permalink raw reply [nested|flat] 3+ messages in thread
end of thread, other threads:[~2022-11-23 09:03 UTC | newest]
Thread overview: 3+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2022-11-17 17:32 Logical replication missing information PG Doc comments form <noreply@postgresql.org>
2022-11-23 02:44 ` Peter Smith <smithpb2250@gmail.com>
2022-11-23 09:03 ` Boboc Cristi <bobocc@yahoo.com>
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