Replies: 1 comment
|
Hi! Short answer: no — as far as Supabase's public docs show, there is no supported endpoint or metric that exposes the managed primary's clock synchronization state, on Free or on any other plan. I could not find anywhere in the docs a last-sync time, an error bound vs UTC, or a step/failover invalidation signal for the primary's clock. What you can verify from inside the database (on any plan, including Free):
What you cannot get: the host's NTP/chrony state (last sync, offset, root dispersion) lives at the OS level, and managed Supabase gives you no host access; the Postgres logs available in the dashboard do not include host NTP events either. Supabase's docs do say every database is set to UTC by default, but that is a timezone setting, not a sync-accuracy guarantee: https://supabase.com/docs/guides/database/postgres/configuration So for a client that needs auditable evidence of a bounded clock error, the honest position is that the database alone cannot provide it. The practical workaround is to sample Happy to dig further if you can share what the client needs the evidence for (audit vs. ordering guarantees, for example) — the right workaround depends on that. Thanks! |
Uh oh!
There was an error while loading. Please reload this page.
I’m evaluating what a client can verify about the clock of a managed Supabase PostgreSQL primary on the Free plan. PostgreSQL’s
clock_timestamp()returns wall-clock time.Is there a supported endpoint or metric tied to the active primary that exposes the following?
If these signals are available on Free, where are they documented, and how can a client verify that they apply to its current primary?
All reactions