Re: Simplify code building the LR conflict messages

Álvaro Herrera <alvherre@kurilemu.de>

From: Álvaro Herrera <alvherre@kurilemu.de>

To: Amit Kapila <amit.kapila16@gmail.com>

Cc: Tom Lane <tgl@sss.pgh.pa.us>, Peter Smith <smithpb2250@gmail.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>

Date: 2025-12-03T14:41:09Z

Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

Improve errdetail for logical replication conflict messages.
- 48efefa6caac 19 (unreleased) landed

On 2025-Dec-01, Amit Kapila wrote:

> The reason for displaying in this style is that, in conflicts, users
> may want to define their custom resolution strategies based on
> conflict_type. Sometimes they need to resolve conflicts manually as
> well. To make an informed decision on which version of the row is
> "correct," the human reviewer needs full context.

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?

-- 
Álvaro Herrera         PostgreSQL Developer  —  https://www.EnterpriseDB.com/