Re: set not null column using existing constraint

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: Marco Piovan <mpiovan(at)workwave(dot)com>
Cc: Rui DeSousa <rui(dot)desousa(at)icloud(dot)com>, "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org>
Subject: Re: set not null column using existing constraint
Date: 2018-01-10 16:13:21
Message-ID: CAKFQuwY4KzV3=xqXQUw3WP68D3DrbN5Ukzt4O=JGH=OjdL26Fw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

On Wednesday, January 10, 2018, Marco Piovan <mpiovan(at)workwave(dot)com> wrote:

> The column is not marked as NOT NULL but a valid constraint "CHECK
> (column IS NOT NULL)" exists.
>
> I haven't found a way to use that specific constraint and avoid the table
> rescan.
>

It probably doesn't exist then, which is not that surprising; no one
foresaw people using a check constraint for not null when an explicit
specifier exists.

David J.

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message flumbador 2018-01-10 16:28:32 Re: Issue on restore / recover
Previous Message Marco Piovan 2018-01-10 16:02:33 Re: set not null column using existing constraint