Hi,

This is follow-up work to patch [1], which fixed a bug in PG19 by allowing 
pg_createsubscriber to accept duplicate publication names, since publication 
names are unique per database.

In the review thread, Amit suggested allowing duplicate subscription names as 
well, because subscription names are also unique per database. However, that 
required more work because when slot names are not specified, subscription 
names are used as slot names, and slot names must be unique per cluster. For 
that reason, the change was deferred to v20.

Here it is. The code changes are actually small. When slot names are specified, 
we can allow duplicate subscription names. Doc and test changes are included. 
See the attached patch for details.

[1] 
https://www.postgresql.org/message-id/B08A7C89-B3DE-4C1D-A671-32AD8BAB7E22%40gmail.com

Best regards,
--
Chao Li (Evan)
HighGo Software Co., Ltd.
https://www.highgo.com/




Attachment: v1-0001-pg_createsubscriber-Allow-duplicate-subscription-.patch
Description: Binary data

Reply via email to