Re: table inheritance versus column compression and storage settings

From: Peter Eisentraut <peter(at)eisentraut(dot)org>
To: Ashutosh Bapat <ashutosh(dot)bapat(dot)oss(at)gmail(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: table inheritance versus column compression and storage settings
Date: 2023-12-05 12:58:10
Message-ID: 38546838-8a60-4d50-ba8e-b2c7cf2cb64b@eisentraut.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
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".

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Drouvot, Bertrand 2023-12-05 13:38:12 Re: Synchronizing slots from primary to standby
Previous Message Peter Eisentraut 2023-12-05 12:52:36 Make attstattarget nullable