Re: table inheritance versus column compression and storage settings
Peter Eisentraut <peter@eisentraut.org>
From: Peter Eisentraut <peter@eisentraut.org>
To: Ashutosh Bapat <ashutosh.bapat.oss@gmail.com>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2023-12-05T12:58:10Z
Lists: pgsql-hackers
On 05.12.23 05:26, Ashutosh Bapat wrote: >> - When inheriting from multiple parents with different settings, an >> explicit setting in the child is required. > When no explicit setting for child is specified, it will throw an > error as it does today. Right? Yes, it would throw an error, but a different error than today, saying something like "the settings in the parents conflict, so you need to specify one here to override the conflict".
Commits
-
Revert "Improve compression and storage support with inheritance"
- 74563f6b9021 17.0 landed
-
Improve compression and storage support with inheritance
- 0413a556990b 17.0 landed
-
Delay build of Memoize hash table until executor run
- 57f59396bb51 17.0 cited
-
Fix locking when fixing an incomplete split of a GIN internal page
- 6a1ea02c491d 17.0 cited