On Tue, Sep 9, 2025 at 9:12 PM Ron Johnson wrote:
> On Tue, Sep 9, 2025 at 8:41 PM Justin wrote:
>
>>
>> XID being 32 bit
>>
>
> Would converting them to 64 bits require changing the on-disk structure of
> database files?
>
Yes this is one of the reasons 64 bit xid has not be used yet. pg_upgr
On Tue, Sep 9, 2025 at 8:41 PM Justin wrote:
> I read through the article its click bait/flame war just waiting to happen.
>
> Article is a list of cherry picked PG drawbacks that can be mitigated or
> worked around.
>
> On the bulk updating. I'm shaking my finger at any one that locks up 25%
>
On Tue, Sep 9, 2025 at 10:27 AM Ellen Allhatatlan <
ellenallhatat...@gmail.com> wrote:
> Reading this article
>
> https://firebirdsql.org/migrating-from-firebird-to-postgresql-what-can-go-wrong-
> I'm a bit confused (not the first time...)
>
> In part 1. Differences in MVCC implementation - he's s
I read through the article its click bait/flame war just waiting to happen.
Article is a list of cherry picked PG drawbacks that can be mitigated or
worked around.
On the bulk updating. I'm shaking my finger at any one that locks up 25%
of a table with an update or delete. That is asking for pro
On Tue, Sep 9, 2025 at 11:57 AM Ellen Allhatatlan <
ellenallhatat...@gmail.com> wrote:
> > Note: your link is wrong, corrected here:
>
> Extra hyphen - sorry about and thanks for pointing it out!
>
> > What the article is driving at is that postgres does not use rollback
> logs to handle updated r
Also reviewing if we really need SERIALIZED and could instead use READ
COMMITTED. Would that be likely to mitigate against this happening?
PostgreSQL can NOT go below READ COMMITTED in transaction isolation
levels. Read Committed is the default mode for all transactions in
PostgreSQL
https://ww
On Mon, Sep 8, 2025 at 12:04 PM Alec Cozens wrote:
> Looking at the postgresql code, the LW lock SerializableFinishedList
> appears to be acquired and then released, usually in the duration of a call
> to a procedure. Base on that (admittedly maybe faulty) view of the code, I
> am surprised to se
> Note: your link is wrong, corrected here:
Extra hyphen - sorry about and thanks for pointing it out!
> What the article is driving at is that postgres does not use rollback logs to
> handle updated records in the MVCC implementation. There are absolutely
> performance tradeoffs in that decis
