Skip site navigation (1) Skip section navigation (2)

Re: Check constraints on non-immutable keys

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Magnus Hagander <magnus(at)hagander(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Check constraints on non-immutable keys
Date: 2010-06-30 15:31:36
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
On Wed, Jun 30, 2010 at 11:02 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Magnus Hagander <magnus(at)hagander(dot)net> writes:
>> On Wed, Jun 30, 2010 at 16:38, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>>> The example seems to me to be in the category of "so don't do that"
>>> rather than something that we need to save users from.  Yes, it's
>> In that case, should we at least throw a warning?
> I don't see a reason to do that.  If we could distinguish actually
> problematic cases from safe cases, it would be helpful, but we can't.
> Moreover, throwing a warning would encourage people to do actively
> *unsafe* things to suppress the warning --- like marking functions
> as immutable when they really aren't.

My scintillating contribution to this discussion is the observation
that unrestorable dumps suck.

A lot.

Robert Haas
The Enterprise Postgres Company

In response to


pgsql-hackers by date

Next:From: Bruce MomjianDate: 2010-06-30 15:39:15
Subject: Re: Keepalives win32
Previous:From: Kevin GrittnerDate: 2010-06-30 15:29:18
Subject: Re: Keepalives win32

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group