Re: Transaction timeout - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: Transaction timeout
Date
Msg-id af8af2ea-a4f5-271e-26e9-01a4584d73d9@eisentraut.org
Whole thread Raw
In response to Re: Transaction timeout  (Andrey Borodin <amborodin86@gmail.com>)
List pgsql-hackers
On 12.01.23 20:46, Andrey Borodin wrote:
>> On Sun, Dec 18, 2022 at 12:53:31PM -0800, Andrey Borodin wrote:
>>> I've rewritten this part to correctly report all timeouts that did
>>> happen. However there's now a tricky comma-formatting code which was
>>> tested only manually.
>> I suspect this will make translation difficult.
> I use special functions for this like _()
> 
> char* lock_reason = lock_timeout_occurred ? _("lock timeout") : "";
> 
> and then
> ereport(ERROR, (errcode(err_code),
>   errmsg("canceling statement due to %s%s%s%s%s", lock_reason, comma1,
>   stmt_reason, comma2, tx_reason)));
> 
> I hope it will be translatable...

No, you can't do that.  You have to write out all the strings separately.



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: lockup in parallel hash join on dikkop (freebsd 14.0-current)
Next
From: Nathan Bossart
Date:
Subject: Re: Inefficiency in parallel pg_restore with many tables