Hi,

Thanks for posting the patch. I feel the logging should be improved, but
it might be out-of-scope. Here I focused on the doc patch.

```
+          or manually roll back the prepared transaction on the subscriber,
+          disable <literal>two_phase</literal> (see
+          <link linkend="sql-altersubscription-params-set"><literal>ALTER 
SUBSCRIPTION ... SET</literal></link>)
+          until that transaction is committed on the publisher and replicated
+          again, and then re-enable <literal>two_phase</literal> if required.
```

Isn't it better to disable the subscription before rolling back? If the 
publisher
runs COMMIT/ROLLBACK PREPARED soon, the resumed apply worker raises
"prepared transaction ... does not exist" error.

Best regards,
Hayato Kuroda
FUJITSU LIMITED



Reply via email to