| From: | shihao zhong <zhong950419(at)gmail(dot)com> |
|---|---|
| To: | Joe Conway <mail(at)joeconway(dot)com> |
| Cc: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Dilip Kumar <dilipbalaut(at)gmail(dot)com>, "Hayato Kuroda (Fujitsu)" <kuroda(dot)hayato(at)fujitsu(dot)com>, Nisha Moond <nisha(dot)moond412(at)gmail(dot)com>, Shveta Malik <shveta(dot)malik(at)gmail(dot)com>, "Zhijie Hou (Fujitsu)" <houzj(dot)fnst(at)fujitsu(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, tomas(at)vondra(dot)me |
| Subject: | Re: Clock-skew management in logical replication |
| Date: | 2024-09-22 18:18:28 |
| Message-ID: | CAGRkXqTef8X=-vNwsqA_B8wFVrkVr_P_iHZkOq4m71vd4nNL6A@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
>
> > Long-term, we should consider integrating with a distributed time
> > service like AWS Time Sync Service. This ensures high accuracy and
> > scalability for demanding applications.
>
> > I think the pluggable access method should make > this possible, no?
> I am sorry that I did not explain clearly in previous email. What do I
> mean is the pluggable time access method should provide the mechanism to
> use customized time service. But there is no out of box solution for
> customer who want to use customized time service. I am suggesting we
> provide some default implementation for popular used time service like AWS
> time sync service. Maybe that should be done outside of the mainstream but
> this is something provide better user experience
>
> --
> Joe Conway
> PostgreSQL Contributors Team
> RDS Open Source Databases
> Amazon Web Services: https://aws.amazon.com
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Shayon Mukherjee | 2024-09-22 18:20:53 | Re: [PATCH] Re: Proposal to Enable/Disable Index using ALTER INDEX |
| Previous Message | Shayon Mukherjee | 2024-09-22 17:42:48 | [PATCH] Re: Proposal to Enable/Disable Index using ALTER INDEX |