| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Mike Lissner <mlissner(at)michaeljaylissner(dot)com>, pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Logical replication DNS cache |
| Date: | 2019-12-12 14:19:14 |
| Message-ID: | 5499f323-8eaa-759a-55c5-9f5ba3829f9a@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 2019-12-12 01:37, Mike Lissner wrote:
> I've got a server at example.com <http://example.com> that currently
> publishes logical replication to a server in AWS RDS. I plan to move the
> server at example.com <http://example.com> so that it has a new IP
> address (but same domain name).
>
> I'm curious if anybody knows how the logical replication subscriber in
> AWS would handle that.
>
> There's at least three layers where the DNS might be cached, creating
> breakage once the move is complete:
>
> - Postgres itself
>
> - AWS's postgresql fork in RDS might have something
>
> - The OS underlying amazon's RDS service
Postgres itself doesn't cache any host name resolution results. I don't
know about the other two pieces.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Арсен Арутюнян | 2019-12-12 14:26:48 | Async_Notify |
| Previous Message | Rich Shepard | 2019-12-12 13:37:59 | Re: Encoding/collation question |