On 2023-Sep-14, bruno da silva wrote:
> This problem is more acute when the FK Table stores a small number of rows
> like types or codes.
Right, because the likelihood of multiple transactions creating
new references to the same row is higher.
> I think in those cases an enum type should be used
This problem is more acute when the FK Table stores a small number of rows
like types or codes.
I think in those cases an enum type should be used instead of a column with
a FK.
Thanks.
On Thu, Sep 14, 2023 at 7:23 AM Alvaro Herrera
wrote:
> On 2023-Sep-13, bruno da silva wrote:
>
> > I just had
On 2023-Sep-13, bruno da silva wrote:
> I just had an outage on postgres 14 due to multixact members limit exceeded.
Sadly, that's not as uncommon as we would like.
> So the documentation says "There is a separate storage area which holds the
> list of members in each multixact, which also uses
On Wed, Sep 13, 2023 at 8:29 AM bruno da silva wrote:
>
> are foreign keys a big source of multixact IDs so not recommended on
> tables with a lot of data and a lot of churn?
>
I am curious to hear other answers or if anything has changed. I
experienced this problem a couple of times on PG 11. I
