Re: StringInfo fixes, v19 edition. Plus a few oddities

From: Peter Smith <smithpb2250(at)gmail(dot)com>
To: vignesh C <vignesh21(at)gmail(dot)com>
Cc: "Hayato Kuroda (Fujitsu)" <kuroda(dot)hayato(at)fujitsu(dot)com>, "Zhijie Hou (Fujitsu)" <houzj(dot)fnst(at)fujitsu(dot)com>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, David Rowley <dgrowleyml(at)gmail(dot)com>, PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Subject: Re: StringInfo fixes, v19 edition. Plus a few oddities
Date: 2026-04-28 05:46:34
Message-ID: CAHut+PvicB-bAqo4XpsPOnr=Li_jop6i4kpcy+VK_MYsEFFeqg@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi Vignesh.

Feedback for v4-0001.

======
src/backend/replication/logical/conflict.c

I guess the following are not strictly the fault of this patch, but I
thought a few of these messages could be improved and made consistent.
Since you are anyway changing most of these messages, now might be the
best time to do it.

e.g.
Current: "Updating the row that was..."

SUGGESTION#1. "Updating a row that was..."
SUGGESTION#2. "Attempting to update a row that was..."
SUGGESTION#3. "The row to be updated was..."

e.g.
Current: "Deleting the row that was..."

SUGGESTION#1. "Deleting a row that was..."
SUGGESTION#2. "Attempting to delete a row that was..."
SUGGESTION#3. "The row to be deleted was..."

~~

And another below (outside the patch) could be updated to be the same:

e.g.
Current: "The row to be updated was deleted by..."

SUGGESTION#1. "Updating a row that was deleted by..."
SUGGESTION#2. "Attempting to update a row that was deleted by..."
SUGGESTION#3. Leave as-is. "The row to be updated was..."

~~~

All those conflict messages should be consistent-looking.

I prefer suggestion #3 because those are also the same as the existing
code comments of the ConflictType enum.

======
Kind Regards,
Peter Smith.
Fujitsu Australia

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bertrand Drouvot 2026-04-28 05:54:47 Re: Fix race condition in pg_get_publication_tables with concurrent DROP TABLE
Previous Message Alena Rybakina 2026-04-28 05:28:45 Re: Vacuum statistics