| From: | Andrey Borodin <amborodin86(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, Michael Paquier <michael(at)paquier(dot)xyz>, Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, Justin Pryzby <pryzby(at)telsasoft(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Something is wrong with wal_compression |
| Date: | 2023-01-28 03:57:35 |
| Message-ID: | CAAhFRxizSbqbciX0025J-35q5-aFi9HXaO5SDPH=fWuPMaT34Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Jan 27, 2023 at 7:40 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> What are you using it for, that you don't care whether the answer
> is trustworthy?
>
It's not trustworthy anyway. Xid wraparound might happen during
reconnect. I suspect we can design a test that will show that it does
not always show correct results during xid->2pc conversion (there is a
point in time when xid is not in regular and not in 2pc, and I'm not
sure ProcArrayLock is held). Maybe there are other edge cases.
Anyway, if a user wants to know the status of xid in case of
disconnection they have prepared xacts.
Best regards, Andrey Borodin.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | houzj.fnst@fujitsu.com | 2023-01-28 04:06:26 | RE: Deadlock between logrep apply worker and tablesync worker |
| Previous Message | Andres Freund | 2023-01-28 03:49:17 | Re: Something is wrong with wal_compression |