Re: Simplify code building the LR conflict messages - Mailing list pgsql-hackers

From Mihail Nikalayeu
Subject Re: Simplify code building the LR conflict messages
Date
Msg-id CADzfLwX7fHaRX5MW1cT2W7f0QXbKcJD55aWTfr3kGO19niLymw@mail.gmail.com
Whole thread Raw
In response to Re: Simplify code building the LR conflict messages  (Álvaro Herrera <alvherre@kurilemu.de>)
List pgsql-hackers
Hello, everyone!

On Wed, Dec 3, 2025 at 3:41 PM Álvaro Herrera <alvherre@kurilemu.de> wrote:
> I think it's odd that conflict resolution depends on log entries.  I
> think it would be much more valuable if conflict reporting would save
> the details of the conflict to some kind of conflict logging table.
> How exactly are we expecting that users would bring the data from the
> log file to a database row, when they are to be merged?  What happens if
> there are bytea columns in the table?

Such a proposal exists already at [0].

Also, sorry for being noisy and a little-bit offtopic but I think it
is a good moment to highlight the fact that such messages are also not
so useful because sometimes they are just clearly incorrect...
You may find details and reproducers at [1] and [2].

Best regards,
Mikhail.

[0]:
https://www.postgresql.org/message-id/flat/CAA4eK1%2B44b3vd_OWfiaVNtjf5Njb5cek09pmKRmttBByeg0NoA%40mail.gmail.com#e74b1b89039c21e64342a7d337128edb
[1]: https://www.postgresql.org/message-id/flat/CADzfLwXZVmbo11tFS_G2i+6TfFVwHU4VUUSeoqb+8UQfuoJs8A@mail.gmail.com
[2]:
https://www.postgresql.org/message-id/flat/CADzfLwVj9ogzrf2P_H9Xb1z8vLEzBemBxp1nC9wCg4KaOFbvmw%40mail.gmail.com#41375b3243460a14bfab55bfead9011e



pgsql-hackers by date:

Previous
From: Ignat Remizov
Date:
Subject: Re: [PATCH] Add enable_copy_program GUC to control COPY PROGRAM
Next
From: Zsolt Parragi
Date:
Subject: Proposal: Add a callback data parameter to GetNamedDSMSegment