On 11/20/18 13:00, Tom Lane wrote:
> If the stored XIDs were 64 bits wide, we'd not have to bother with all
> of this mess ... but adding another 64 bits to tuple headers would be
> a painful space cost, not to mention the storage compatibility issues.
People keep saying that. But didn't someone
Martín
On Tue, Nov 20th, 2018 at 6:0 PM, Tom Lane wrote:
>
>
>
> =?UTF-8?q?Mart=C3=ADn_Fern=C3=A1ndez?= < fmarti...@gmail.com > writes:
> > First thing that generated a lot of noise in my head was the following,
> if pg assigns contiguous numeric values for the txid, how does pg deal
> with
=?UTF-8?q?Mart=C3=ADn_Fern=C3=A1ndez?= writes:
> First thing that generated a lot of noise in my head was the following, if pg
> assigns contiguous numeric values for the txid, how does pg deal with
> fragmentation issues ? Then I later found that the txid space is actually
> circular and not
Hello everyone, second time writing to this awesome mailing list.
I’m helping manage a postgresql 9.2.24 high volume transaction database and
yesterday we were literally one hour away of having to deal with transaction id
wraparound. We were really lucky about identifying the issue one hour
