Re: Identify missing publications from publisher while create/alter subscription.

Just wondering if we should also be detecting the incorrect conninfo

set with ALTER SUBSCRIPTION command as well. See below:

-- try creating a subscription with incorrect conninfo. the command fails.

postgres=# create subscription sub1 connection 'host=localhost

port=5490 dbname=postgres' publication pub1;

ERROR:  could not connect to the publisher: connection to server at

"localhost" (::1), port 5490 failed: Connection refused

    Is the server running on that host and accepting TCP/IP connections?

connection to server at "localhost" (127.0.0.1), port 5490 failed:

Connection refused

    Is the server running on that host and accepting TCP/IP connections?

-- reset the connninfo in the subscription to some wrong value. the

command succeeds.

postgres=# alter subscription sub1 connection 'host=localhost

port=5490 dbname=postgres';

ALTER SUBSCRIPTION

postgres=#

postgres=# drop subscription sub1;

ERROR:  could not connect to publisher when attempting to drop

replication slot "sub1": connection to server at "localhost" (::1),

port 5490 failed: Connection refused

    Is the server running on that host and accepting TCP/IP connections?

connection to server at "localhost" (127.0.0.1), port 5490 failed:

Connection refused

    Is the server running on that host and accepting TCP/IP connections?

HINT:  Use ALTER SUBSCRIPTION ... SET (slot_name = NONE) to

disassociate the subscription from the slot.