Launch HN: Ardent (YC P26) – Postgres sandboxes in seconds with zero migration

Re:Launch HN: Ardent (YC P26) – Postgres sandboxes in second... by mnahkies on Wednesday May 13, 2026 @04:28PM (#48127051)

I wanted to try doing something similar to this in our dev environment (think shared dev database but per branch clones), but this limitation seemed tricky to accept:

> The source database can't have any active connections during cloning.

I wouldn't mind some lock contention, but having to kill all connections seemed a bit harsh

[ Parent | on HN ]

Re:Launch HN: Ardent (YC P26) – Postgres sandboxes in second... by IdontKnowRust on Thursday May 14, 2026 @08:00AM (#48134181)

I guess it's still possible with a replica that no one is using?

So you don't need to touch real production db?

Not sure if it applies for all use cases tou

[ Parent | on HN ]

Re:Launch HN: Ardent (YC P26) – Postgres sandboxes in second... by mnahkies on Friday May 15, 2026 @04:26AM (#48145975)

Yeah I think a read replica might fit the bill - though I suspect active logical replication counts as a connection in this context.

Using a cloud provider read replica might not (as I think that might use block level replication) - but then you're paying for an extra dev database host for the privilege

[ Parent | on HN ]