Re: Fix log_line_prefix to display the transaction id (%x) for statements not in a transaction block

From: Quan Zongliang <quanzongliang(at)yeah(dot)net>
To: jian he <jian(dot)universality(at)gmail(dot)com>, "Andrey M(dot) Borodin" <x4mmm(at)yandex-team(dot)ru>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Fix log_line_prefix to display the transaction id (%x) for statements not in a transaction block
Date: 2024-04-16 07:15:57
Message-ID: 41b00754-0bbd-4a11-b9e7-fbff5b5bf5b7@yeah.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2024/3/11 09:25, Quan Zongliang wrote:
>
>
> On 2024/3/4 15:48, jian he wrote:
>
>> Maybe we can tolerate LOG, first output the query plan then statement.
>>
> It is more appropriate to let the extension solve its own problems.
> Of course, this change is not easy to implement.
> Due to the way XID is assigned, there seems to be no good solution at
> the moment.
>
>
According to the discussion with Jian He. Use the guc hook to check if
the xid needs to be output. If needed, the statement log can be delayed
to be output.

Attachment Content-Type Size
postgres-v3.patch text/plain 4.3 KB

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Bertrand Drouvot 2024-04-16 07:29:32 Re: Disallow changing slot's failover option in transaction block
Previous Message Stefan Fercot 2024-04-16 07:09:55 Re: pg_combinebackup fails on file named INCREMENTAL.*