From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Peter Smith <smithpb2250(at)gmail(dot)com> |
Cc: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: create subscription - improved warning message |
Date: | 2022-10-10 14:44:41 |
Message-ID: | 4072660.1665413081@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Peter Smith <smithpb2250(at)gmail(dot)com> writes:
> On Mon, Oct 10, 2022 at 4:04 PM Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> wrote:
>> I think the below gives accurate information:
>> WARNING: subscription was created, but is not connected
>> HINT: You should create the slot manually, enable the subscription,
>> and run %s to initiate replication.
> +1
It feels a little strange to me that we describe two steps rather vaguely
and then give exact SQL for the third step. How about, say,
HINT: To initiate replication, you must manually create the replication
slot, enable the subscription, and refresh the subscription.
Another idea is
HINT: To initiate replication, create the replication slot on the
publisher, then run ALTER SUBSCRIPTION ... ENABLE and ALTER
SUBSCRIPTION ... REFRESH PUBLICATION.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2022-10-10 14:58:37 | Re: Turn TransactionIdRetreat/Advance into inline functions |
Previous Message | Tom Lane | 2022-10-10 14:34:23 | Re: src/test/perl/PostgreSQL/Test/*.pm not installed |