| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andrey Borodin <amborodin86(at)gmail(dot)com> |
| Cc: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, Justin Pryzby <pryzby(at)telsasoft(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org, Michael Paquier <michael(at)paquier(dot)xyz> |
| Subject: | Re: Something is wrong with wal_compression |
| Date: | 2023-01-27 00:23:04 |
| Message-ID: | 3236345.1674778984@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Andrey Borodin <amborodin86(at)gmail(dot)com> writes:
> On Thu, Jan 26, 2023 at 3:04 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> Indeed, it seems like this behavior makes pg_xact_status() basically
>> useless as things stand.
> If we agree that xid allocation is not something persistent, let's fix
> the test?
If we're not going to fix this behavior, we need to fix the docs
to disclaim that pg_xact_status() is of use for what it's said
to be good for.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2023-01-27 00:30:26 | Re: Partition key causes problem for volatile target list query |
| Previous Message | Tom Lane | 2023-01-27 00:21:16 | Re: Partition key causes problem for volatile target list query |