| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | Jeff Davis <pgsql(at)j-davis(dot)com>, Jeff Davis <jdavis(at)postgresql(dot)org>, pgsql-committers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: pgsql: Trial fix for old cross-version upgrades. |
| Date: | 2025-02-23 19:17:10 |
| Message-ID: | 1144186.1740338230@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> On 2025-02-22 Sa 9:20 PM, Tom Lane wrote:
>> I'm not really seeing a better answer than hacking the comparison
>> rules to ignore the relallvisible difference for these tables.
>> That's darn ugly, and I suspect the implementation will be messy,
>> but do we have another way?
> Having slept on it I can't see anything better. It's only for very old
> branches, and nothing is really going wrong here, so ignoring the
> difference seems quite reasonable.
Agreed, and done.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2025-02-24 00:54:46 | pgsql: Remove read/sync fields from pg_stat_wal and GUC track_wal_io_ti |
| Previous Message | Tom Lane | 2025-02-23 19:16:33 | pgsql: Ignore hash's relallvisible when checking pg_upgrade from pre-v1 |