From: | yudhi s <learnerdatabase99(at)gmail(dot)com> |
---|---|
To: | sud <suds1434(at)gmail(dot)com> |
Cc: | Muhammad Salahuddin Manzoor <salahuddin(dot)m(at)bitnine(dot)net>, pgsql-general <pgsql-general(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Long running query causing XID limit breach |
Date: | 2024-05-23 07:19:00 |
Message-ID: | CAEzWdqc9gwq0KwqkaZJ9hVH4bhP_RdKPVWsqzA=a8cOh_Njj=g@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Thu, May 23, 2024 at 11:42 AM sud <suds1434(at)gmail(dot)com> wrote:
>
>> Calculation Rationale
>> Daily XID Usage: Approximately 4 billion rows per day implies high XID
>> consumption.
>> Buffer Time: At 1 billion XIDs, you would still have 1 billion XIDs
>> remaining, giving you roughly 12 hours to address the issue if your system
>> consumes 200 million XIDs per hour.
>>
>>
>>
>
> OP mentioned that initially the number of business transactions is around
500million but the rows inserted across many tables are ~4-5billion in
total per day. So doesn't it mean that the XID consumption will happen
based on the transactions rather on the number of rows basis. Say
for example ~4billion rows may be loaded using a batch size of ~1000 using
bulk load, so that will be ~4million txn so it should use ~4million XID but
not 4 billion XID usage. And thus making the transactions process in
batches rather than row by row minimizes the XID usage. Correct?
From | Date | Subject | |
---|---|---|---|
Next Message | Laurenz Albe | 2024-05-23 07:52:31 | Re: Long running query causing XID limit breach |
Previous Message | Peter J. Holzer | 2024-05-23 07:06:49 | expected authentication request from server, but received H |