|
- <?xml version="1.0" encoding="UTF-8" standalone="no"?>
- <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>30.3. Conflicts</title><link rel="stylesheet" type="text/css" href="stylesheet.css" /><link rev="made" href="pgsql-docs@lists.postgresql.org" /><meta name="generator" content="DocBook XSL Stylesheets V1.79.1" /><link rel="prev" href="logical-replication-subscription.html" title="30.2. Subscription" /><link rel="next" href="logical-replication-restrictions.html" title="30.4. Restrictions" /></head><body><div xmlns="http://www.w3.org/TR/xhtml1/transitional" class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="5" align="center">30.3. Conflicts</th></tr><tr><td width="10%" align="left"><a accesskey="p" href="logical-replication-subscription.html" title="30.2. Subscription">Prev</a> </td><td width="10%" align="left"><a accesskey="u" href="logical-replication.html" title="Chapter 30. Logical Replication">Up</a></td><th width="60%" align="center">Chapter 30. Logical Replication</th><td width="10%" align="right"><a accesskey="h" href="index.html" title="PostgreSQL 12.4 Documentation">Home</a></td><td width="10%" align="right"> <a accesskey="n" href="logical-replication-restrictions.html" title="30.4. Restrictions">Next</a></td></tr></table><hr></hr></div><div class="sect1" id="LOGICAL-REPLICATION-CONFLICTS"><div class="titlepage"><div><div><h2 class="title" style="clear: both">30.3. Conflicts</h2></div></div></div><p>
- Logical replication behaves similarly to normal DML operations in that
- the data will be updated even if it was changed locally on the subscriber
- node. If incoming data violates any constraints the replication will
- stop. This is referred to as a <em class="firstterm">conflict</em>. When
- replicating <code class="command">UPDATE</code> or <code class="command">DELETE</code>
- operations, missing data will not produce a conflict and such operations
- will simply be skipped.
- </p><p>
- A conflict will produce an error and will stop the replication; it must be
- resolved manually by the user. Details about the conflict can be found in
- the subscriber's server log.
- </p><p>
- The resolution can be done either by changing data on the subscriber so
- that it does not conflict with the incoming change or by skipping the
- transaction that conflicts with the existing data. The transaction can be
- skipped by calling the <a class="link" href="functions-admin.html#PG-REPLICATION-ORIGIN-ADVANCE">
- <code class="function">pg_replication_origin_advance()</code></a> function with
- a <em class="parameter"><code>node_name</code></em> corresponding to the subscription name,
- and a position. The current position of origins can be seen in the
- <a class="link" href="view-pg-replication-origin-status.html" title="51.80. pg_replication_origin_status">
- <code class="structname">pg_replication_origin_status</code></a> system view.
- </p></div><div class="navfooter"><hr /><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="logical-replication-subscription.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="logical-replication.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="logical-replication-restrictions.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">30.2. Subscription </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 30.4. Restrictions</td></tr></table></div></body></html>
|
