Re: Extra check in 9.0 exclusion constraint unintended consequences - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Extra check in 9.0 exclusion constraint unintended consequences
Date
Msg-id CA+TgmoYR2TQHxa=PqcN=J7e3eTPd4ajK0GcvXPCFoisUaHmXhg@mail.gmail.com
Whole thread Raw
In response to Re: Extra check in 9.0 exclusion constraint unintended consequences  (Jeff Davis <pgsql@j-davis.com>)
Responses Re: Extra check in 9.0 exclusion constraint unintended consequences  (Jeff Davis <pgsql@j-davis.com>)
List pgsql-hackers
On Fri, Jul 8, 2011 at 12:58 AM, Jeff Davis <pgsql@j-davis.com> wrote:
> On Thu, 2011-07-07 at 12:36 -0400, Robert Haas wrote:
>> I think it's probably too late to go fiddling with the behavior of 9.0
>> at this point.  If we change the text of error messages, there is a
>> chance that it might break applications; it would also require those
>> messages to be re-translated, and I don't think the issue is really
>> important enough to justify a change.
>
> Good point on the error messages -- I didn't really think of that as a
> big deal.
>
>> I am happy to see us document
>> it better, though, since it's pretty clear that there is more
>> likelihood of hitting that error than we might have suspected at the
>> outset.
>
> Doc patch attached, but I'm not attached to the wording. Remember that
> we only need to update the 9.0 docs, I don't think you want to apply
> this to master (though I'm not sure how this kind of thing is normally
> handled).

I'm wondering if we might want to call this out with a <note> or
similar...  especially if we're only going to put it into the 9.0
docs.

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


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: dropping table in testcase alter_table.sql
Next
From: Robert Haas
Date:
Subject: Re: [GENERAL] Creating temp tables inside read only transactions