-
Notifications
You must be signed in to change notification settings - Fork 153
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Pglogical 2.1.1 CONFLICT: remote UPDATE on relation ... DETAIL: existing local tuple #150
Comments
Do you had any news about that? Got the same issue with the 2.2.0 release. |
Haven't had time to look yet, there's a great deal going on and priorities are spread a bit thin. A test case SQL script would be handy. |
Thx for the reply. I have exactly the same issue but I have no idea where it comes from... can't really reproduce it mounting a new database... |
Same problem here.
Version Info:
|
Was this issue ever resolved - as I'm experiencing something very similar. I've narrowed it down to only occurring when using certain key value prefixes of the tables in question - strange but apparently true... |
Hi @paulbandler, what did you mean with "using certain key value prefixes of the tables in question"? Is there any news about this issue? Same problem.
Version Info:
|
Hello guys, I am having the same issues but I do not know what is going on. I have a one provider--> subscriber node but I see this error in the logs on the subscriber logs. When I do a count on a table I see the count on subscriber smaller than provider.please anyone has an idea? |
I have the same problem. Update a record at the provider that doesn't exist at the subscriber (for some reason). Is there any way to configure pglogical to download missing records? |
Have a similar issue on multiple tables. All have primary keys. Interestingly, everything was working fine for a week, however we had to increase CPU cores on a system and after the reboot this started happening and the replication stopped. Clocks on both systems are synchronized.
Setup on both provider and subscriber:
Have changed to the following setting and replication is working again:
I don't know why using SPI works -- but it does. Tried switching back to earlier settings and it works for some time and then gives a similar error and replication stops. However, after turning on use_spi we started to see continuous warnings in the log (Snapshot still active). Have logged a separate issue for this. #404 |
I have similar experience with that "CONFLICT" message. I believe on the
latest version of pg_logical you get that "error" every time an UPDATE is
applied on a subscribing server, even though there is no conflict (in my
way of thinkn ing)_.
…On Wed, Nov 30, 2022 at 3:05 AM Gautam Kachru ***@***.***> wrote:
Have a similar issue on multiple tables. All have primary keys.
Interestingly, everything was working fine for a week, however we had to
increase CPU cores on a system and after the reboot this started happening.
Clocks on both systems are synchronized.
pglogical apply 1889269:4258465055_error: CONFLICT: remote UPDATE on relation public.my_table_name. Resolution: apply_remote.
pglogical apply 1889269:4258465055_detail: existing local tuple ...
Setup on both provider and subscriber:
Postgresql: 14.6
Pglogical: 2.4.2
track_commit_timestamp = true
conflict_resolution = 'last_update_wins'
Have changed to the following setting and replication is working again:
conflict_resolution = 'error'
use_spi = true
However, after the above changes we started to see continuous warnings in
the log (Snapshot still active). Have logged a separate issue for this.
#404 <#404>
—
Reply to this email directly, view it on GitHub
<#150 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAMWOHUMFXCOJ6HCBOVICQ3WK4DFBANCNFSM4ETFRFFA>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Still relevant in 2.4.4
|
Also crashed with
Now I'm stuck in the state:
|
i'm using version pglogical 2.1.1 to deploy the model 2 node postgres provider -> subscribe
When the provider that runs 1 dml updates an existing row, subscribe appears as an error :
Let me know what's going on
Thanks All
The text was updated successfully, but these errors were encountered: