On Wed, Jul 22, 2026 at 8:16 AM vignesh C <[email protected]> wrote: > > The attached patch has the changes for the same. This patch also fixes > the issue reported by Kuroda-san at [1]. >
The patch used two different error codes (ERRCODE_FEATURE_NOT_SUPPORTED and ERRCODE_OBJECT_NOT_IN_PREREQUISITE_STATE) for the same condition. I preferred to use ERRCODE_OBJECT_NOT_IN_PREREQUISITE_STATE in both places because the error is about the remote server's state (it isn't new enough), not about a capability this backend fails to implement. That's exactly what OBJECT_NOT_IN_PREREQUISITE_STATE is for, and it's what the existing publisher-version guards use. OTOH, FEATURE_NOT_SUPPORTED reads as "PostgreSQL doesn't implement this" — misleading here, since sequence sync is implemented; the publisher just predates it. I made this change and slightly changed the comments in the patch. See attached. -- With Regards, Amit Kapila.
v6-0001-Reject-sequence-synchronization-against-pre-Postg.patch
Description: Binary data
