| From: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
|---|---|
| To: | David Christensen <david(at)endpoint(dot)com> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Documentation patch for ALTER SUBSCRIPTION |
| Date: | 2020-02-05 02:45:41 |
| Message-ID: | CAA4eK1+55iRMH7+We-Eiup0ur3xGzTOvXQR=qqBP6HSgv8MvxA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Jan 24, 2020 at 2:05 AM David Christensen <david(at)endpoint(dot)com> wrote:
>
> Greetings,
>
> Enclosed find a documentation patch that clarifies the behavior of ALTER SUBSCRIPTION … REFRESH PUBLICATION with new tables; I ran into a situation today where the docs were not clear that existing tables would not be re-copied, so remedying this situation.
>
It seems this is already covered in REFRESH PUBLICATION, see "This
will start replication of tables that were added to the subscribed-to
publications since the last invocation of REFRESH PUBLICATION or since
CREATE SUBSCRIPTION.". As far as I understand, this text explains the
situation you were facing. Can you explain why the text quoted by me
is not sufficient?
--
With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Christensen | 2020-02-05 03:14:30 | Re: Documentation patch for ALTER SUBSCRIPTION |
| Previous Message | Amit Kapila | 2020-02-05 02:36:31 | Re: closesocket behavior in different platforms |