| From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
|---|---|
| To: | bruno da silva <brunogiovs(at)gmail(dot)com> |
| Cc: | pgsql-performance(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Multixact wraparound monitoring |
| Date: | 2023-09-15 09:48:47 |
| Message-ID: | 202309150948.c7fwqegp2f4i@alvherre.pgsql |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
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)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Achilleas Mantzios - cloud | 2023-09-15 14:30:39 | pgsql 10.23 , different systems, same table , same plan, different Buffers: shared hit |
| Previous Message | bruno da silva | 2023-09-14 19:35:10 | Re: Multixact wraparound monitoring |