ger, we could wait
indefinitely (if the parent service has no more incoming transactions,
which means no more WAL to replay).
Are you recommending that we wait until another transaction happens on the
parent DB?
Thanks,
Sean
On Mon, Mar 22, 2021 at 3:59 AM Kyotaro Horiguchi
wrote:
> At
We've noticed what may be a regression / bug in PG13.
I work at Heroku on the Data team, where we manage a fleet of Postgres
services. This change has resulted in breaking the UX we offer to customers
to manage their PG services. In particular, ‘forks’ and ‘point in time
restores’ seem broken for
