On Fri, May 10, 2024 at 08:10:58PM +, Karoline Pauls wrote:
> On Friday, 10 May 2024 at 20:17, Bruce Momjian
> wrote:
> >
> > log_line_prefix supports application name --- why would you not use
> > that?
> >
>
> log_line_prefix is effective in the server log. This change is mostly
> about
Karoline Pauls writes:
> On Friday, 10 May 2024 at 20:17, Bruce Momjian wrote:
>> log_line_prefix supports application name --- why would you not use
>> that?
> log_line_prefix is effective in the server log. This change is mostly about
> improving the message sent back to the client. While
On Friday, 10 May 2024 at 20:17, Bruce Momjian wrote:
>
> log_line_prefix supports application name --- why would you not use
> that?
>
log_line_prefix is effective in the server log. This change is mostly about
improving the message sent back to the client. While the server log is also
On Thu, May 9, 2024 at 11:44:03PM +, Karoline Pauls wrote:
> As we know, the deadlock error message isn't the most friendly one. All the
> client gets back is process PIDs, transaction IDs, and lock types. You have to
> check the server log to retrieve lock details. This is tedious.
>
> In
As we know, the deadlock error message isn't the most friendly one. All the
client gets back is process PIDs, transaction IDs, and lock types. You have to
check the server log to retrieve lock details. This is tedious.
In one of my apps I even added a deadlock exception handler on the app side
