Re: table inheritance versus column compression and storage settings - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: table inheritance versus column compression and storage settings
Date
Msg-id 38546838-8a60-4d50-ba8e-b2c7cf2cb64b@eisentraut.org
Whole thread Raw
In response to Re: table inheritance versus column compression and storage settings  (Ashutosh Bapat <ashutosh.bapat.oss@gmail.com>)
Responses Re: table inheritance versus column compression and storage settings
List 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".




pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Make attstattarget nullable
Next
From: "Drouvot, Bertrand"
Date:
Subject: Re: Synchronizing slots from primary to standby