From: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
---|---|
To: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | logical rep worker for table sync can start and stop very frequently unexpectedly |
Date: | 2017-04-11 17:05:21 |
Message-ID: | CAHGQGwGKz2pz1jRDCTcLNdHTK1es+2ko-qsNY++c_21U+atZtQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi,
I observed $subject when I ran the following steps.
1. start the publisher server
2. start the subscriber server
3. create table with primary key and publication for it
4. insert several records into the table
5. create table with primary key and subscription
6. wait for table sync to finish
7. drop the subscription and recreate the subscription
Then the launcher starts the worker, and the worker starts
another worker for table sync. But that worker for table sync
exits immediately because of primary key violation.
Then the worker tries to start new worker for table sync immediately
and it also exits immediately because of primary key violation.
This sequence repeats very fast...
Attached is the script that I used to reproduce the issue.
Regards,
--
Fujii Masao
Attachment | Content-Type | Size |
---|---|---|
test.sh | application/x-sh | 767 bytes |
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2017-04-11 17:08:39 | Re: strange parallel query behavior after OOM crashes |
Previous Message | Tom Lane | 2017-04-11 16:51:29 | Re: Reversed sync check in pg_receivewal |