PG Flexible Server - Getting timestamp for latest restore point (now)

Question

PG Flexible Server - Getting timestamp for latest restore point (now)

Veruska 10

Hello,

We've recently tested restoring an Postgresql Flexible server from the Azure portal, but when we chose the option for "latest restore point (now)", we realized we don't get to know the timestamp that it's using to restore the instance.

Trying to find in your documentation if it's possible to get the latest timestamp, it doesn't seem possible from either the portal or az cli. For example when restoring a SQL Managed instance database, it tells us what's the latest available backup. Is there anything similar we can get for Postgresql?

Thanks for the information you could provide.

SAI JAGADEESH KUDIPUDI 1,600 Reputation points Microsoft External Staff Moderator

2026-03-23T09:10:08.54+00:00
Hi Veruska,
In Azure Database for PostgreSQL – Flexible Server, the “Latest restore point (Now)” option is intentionally treated as “restore to the newest point the service can recover to at restore time,” and the portal workflow does not surface a fixed timestamp for that target.

The official guidance for “latest restore point” describes the operation as restoring the most recent snapshot and then bringing the new server up with the most recent data available at the time the restore is triggered, but it does not provide a “latest backup timestamp” field like Azure SQL MI does.
what “Latest (Now)” actually means (deep dive, but short)

Flexible Server PITR is based on snapshot backups + transaction logs (WAL).
Microsoft documents that the service:

Takes snapshot backups of the data files (snapshot-based; currently once daily, with behavior that can take an immediate snapshot after modifications), and

Archives transaction logs (WAL) when a WAL segment is ready, then uses those logs during restore to reach the requested point-in-time.

During PITR, the platform first restores the database files from the appropriate snapshot, then performs recovery by replaying WAL to reach a consistent state at (or near) the requested time. Because WAL archival frequency depends on workload, Microsoft notes the RPO delay can be up to ~5 minutes in general—so “Latest” can be slightly behind the wall-clock moment you clicked restore.

How to get an explicit timestamp (best workaround)

If you need a known timestamp, use “Select a custom restore point” instead of “Latest.” Microsoft documents that for Custom restore point, the latest time in UTC is automatically selected by default, which gives you an explicit timestamp you can record/copy for audit/runbooks.

If you want a timestamp that is explicitly chosen from full backups only, use Fast restore, which provides a list of full-backup timestamps you can pick from.
Microsoft reference links

Restore to latest restore point (Flexible Server) [learn.microsoft.com]

Backup and restore concepts (snapshots, WAL, PITR behavior, RPO) [learn.microsoft.com]

Restore full backup (fast restore) – choose from backup timestamps [learn.microsoft.com]
Veruska 10 Reputation points

2026-03-23T13:30:08.6966667+00:00

Hi @SAI JAGADEESH KUDIPUDI ,

I've replied to the message. Thanks
SAI JAGADEESH KUDIPUDI 1,600 Reputation points Microsoft External Staff Moderator

2026-03-27T01:24:27.39+00:00

Hi Veruska,
I hope you had a chance to review the information shared earlier, and I hope this information has been helpful! If you still have questions, please let us know what is needed in the comments so the question can be answered.
Santhosh Kumar Machukuri 0 Reputation points Microsoft External Staff Moderator

2026-04-01T22:11:33.9366667+00:00

Hi Veruska,

I hope you are doing well. Please consider this as a gentle follow up. Kindly let us know if you had got a chance to review the information shared earlier by the engineer Jagadeesh, and I hope this information has been helpful! If you still have questions, feel free. Looking forward to your response.