Re: Something is wrong with wal_compression

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
Cc: Michael Paquier <michael(at)paquier(dot)xyz>, Andrey Borodin <amborodin86(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-27 03:22:25
Message-ID: 3256386.1674789745@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Thomas Munro <thomas(dot)munro(at)gmail(dot)com> writes:
> On Fri, Jan 27, 2023 at 3:04 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> I think we need to get the thing correct first and worry about
>> performance later. What's wrong with simply making pg_xact_status
>> write and flush a record of the XID's existence before returning it?
>> Yeah, it will cost you if you use that function, but not if you don't.

> It would be pg_current_xact_id() that would have to pay the cost of
> the WAL flush, not pg_xact_status() itself,

Right, typo on my part.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Yuya Watari 2023-01-27 03:48:30 Re: [PoC] Reducing planning time when tables have many partitions
Previous Message David Rowley 2023-01-27 03:19:06 Re: Monotonic WindowFunc support for ntile(), percent_rank() and cume_dist()