From: Jürgen Strobel <juergen+postgresql@strobel.info>
To: Tom Lane <tgl@sss.pgh.pa.us>
To: Alvaro Herrera <alvherre@2ndquadrant.com>
Cc: Amit Langote <Langote_Amit_f8@lab.ntt.co.jp>
Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Subject: Re: BUG #15212: Default values in partition tables don't work as expected and allow NOT NULL violation
Date: Tue, 13 Nov 2018 00:06:45 +0100
Message-ID: <ebcf4a32-cfee-8a8f-525d-6ceaa72c75d8@strobel.info> (raw)
In-Reply-To: <5662.1542040384@sss.pgh.pa.us>
References: <20181112140051.yv5m77esq5jz6rkg@alvherre.pgsql>
<5662.1542040384@sss.pgh.pa.us>
On 2018-11-12 17:33, Tom Lane wrote:
> Alvaro Herrera <alvherre@2ndquadrant.com> writes:
>> One of the guiding principles that I think we should hold for
>> partitioning is that operating directly into the partition should be
>> seen as only an optimization compared to inserting into the parent table
>> -- thus it should not behave differently. Applying different default
>> values depending on where you're inserting into goes counter to that
>> principle.
>
> I'm not entirely convinced that I buy that argument, especially not in
> a case like this where it introduces logical inconsistencies where there
> otherwise wouldn't be any.
>
I think I missed something, what are the *introduced* logical problems?
Apart from implementation issues the only logical problems I see are if
you allow to change defaults of the partition key columns, and these are
problematic (nonsensical really) in either case.
Regards,
Jürgen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: juergen+postgresql@strobel.info, tgl@sss.pgh.pa.us, alvherre@2ndquadrant.com, Langote_Amit_f8@lab.ntt.co.jp, pgsql-hackers@lists.postgresql.org
Subject: Re: BUG #15212: Default values in partition tables don't work as expected and allow NOT NULL violation
In-Reply-To: <ebcf4a32-cfee-8a8f-525d-6ceaa72c75d8@strobel.info>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox