Re: BUG #16158: Check constraints using SQL functions work incorrectly

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
Cc: pjander2(at)gmail(dot)com, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: BUG #16158: Check constraints using SQL functions work incorrectly
Date: 2019-12-10 15:39:59
Message-ID: 6508.1575992399@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

"David G. Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> writes:
> You should read the most current version of the documentation for a feature
> before reporting a bug. In this case the warnings you desired have been
> added to more recently versions of the documentation.

Hm, I was thinking that that text had been there for awhile --- certainly
it's not a new restriction. I wonder why we didn't back-patch it?

regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Tomas Vondra 2019-12-10 17:32:24 Re: BUG #16104: Invalid DSA Memory Alloc Request in Parallel Hash
Previous Message Tom Lane 2019-12-10 15:14:31 Re: BUG #16158: Check constraints using SQL functions work incorrectly