From: Alvaro Herrera <alvherre@alvh.no-ip.org>
To: bruno da silva <brunogiovs@gmail.com>
Cc: pgsql-performance@lists.postgresql.org
Subject: Re: Multixact wraparound monitoring
Date: Fri, 15 Sep 2023 11:48:47 +0200
Message-ID: <202309150948.c7fwqegp2f4i@alvherre.pgsql> (raw)
In-Reply-To: <CAB+Nuk-_B_0fTftpqtPxOQGWqUfJYpXQgWGNLK9Nr=z04zjYMw@mail.gmail.com>
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 instead of a column with
> a FK.
Right, that alleviates the issue, but IMO it's a workaround whose need
is caused by a deficiency in our implementation.
--
Álvaro Herrera PostgreSQL Developer — https://www.EnterpriseDB.com/
"Pido que me den el Nobel por razones humanitarias" (Nicanor Parra)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: alvherre@alvh.no-ip.org, brunogiovs@gmail.com, pgsql-performance@lists.postgresql.org
Subject: Re: Multixact wraparound monitoring
In-Reply-To: <202309150948.c7fwqegp2f4i@alvherre.pgsql>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox