| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com> |
| Cc: | Greg Burd <greg(at)burd(dot)me>, Yugo Nagata <nagata(at)sraoss(dot)co(dot)jp>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Support for 8-byte TOAST values, round two |
| Date: | 2026-09-19 00:03:31 |
| Message-ID: | aq3RU3wN5qG62eO8@paquier.xyz |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Sep 17, 2026 at 12:03:00PM -0700, Bharath Rupireddy wrote:
> Another approach is a new test module in src/test/modules (similar to
> the xid_wraparound module) with a simple SQL function that advances
> the OID counter in shared memory, similar to core's SetNextObjectId().
> Being a test module, it doesn't impact production systems, and all the
> 8-byte TOAST chunk_id related tests added for this feature can be
> moved here and run across all BF animals.
That could be one thing. Yes. Or perhaps not.
> Others may have a different opinion. Meanwhile, IMHO, the remaining
> v18 tests can go in, with this discussed separately.
OK, you're right that it also sucks to do nothing for the logical
decoding. So I think that I'll just do something for the
test_decoding TAP test. I am less convinced about the dump/restore
tests you are proposing; these are utterly bloated.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bharath Rupireddy | 2026-09-19 00:26:45 | Re: Support for 8-byte TOAST values, round two |
| Previous Message | Michael Paquier | 2026-09-18 23:56:44 | Re: PG 19 status blog report |