On 2021/03/22 21:40, Sean Jezewski wrote:
Hi Kyotaro -
Thanks for the response.
I think it boils down to your comment:
> I'm not sure. The direct cause of the "issue" is a promotion trigger
> that came before reaching recovery target. That won't happen if the
> "someone" doesn't do
Hi Kyotaro -
Thanks for the response.
I think it boils down to your comment:
> I'm not sure. The direct cause of the "issue" is a promotion trigger
> that came before reaching recovery target. That won't happen if the
> "someone" doesn't do that.
I think the question is 'under what
At Thu, 18 Mar 2021 17:59:34 -0400, Sean Jezewski
wrote in
> 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
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
