Re: NOT NULL constraints in foreign tables

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
Cc: Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: NOT NULL constraints in foreign tables
Date: 2012-08-17 19:44:29
Message-ID: CA+TgmoZ8zft8ks6PJiHd0JiFJEJ-krYQYSegbwhX9dYUaVLaeQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Aug 17, 2012 at 2:58 PM, Alvaro Herrera
<alvherre(at)2ndquadrant(dot)com> wrote:
> I mean, what are NOT NULL in foreign tables for? Are they harmed or
> helped by having pg_constraint rows?

As I've mentioned when this has come up before, I think that
constraints on foreign tables should be viewed as declarative
statements about the contents of the foreign data that the DB will
assume true. This could be useful for a variety of purposes:
constraint exclusion, query optimization, etc.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2012-08-17 19:45:34 Re: ALTER TABLE lock strength reduction patch is unsafe
Previous Message Tom Lane 2012-08-17 19:19:34 Re: NOT NULL constraints in foreign tables