Re: missing locking in at least INSERT INTO view WITH CHECK

From: Andres Freund <andres(at)anarazel(dot)de>
To: Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: missing locking in at least INSERT INTO view WITH CHECK
Date: 2015-08-27 18:29:15
Message-ID: 20150827182915.GK2435@awork2.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2015-08-27 19:19:35 +0100, Dean Rasheed wrote:
> It also seems to me that this warning has proved its worth

Same here - I plan to re-submit it. Perhaps the number of bugs it found
convinces Tom, after I address some of his points.

> although I don't think it's something a production build should be
> producing. Perhaps it could be an Assert?

It's currently protected by a #ifdef USE_ASSERT_CHECKING. A warning
seems to make it easier to actually run the whole regression test, and
it's consistent with what we do in a bunch of other places.

Greetings,

Andres Freund

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Dean Rasheed 2015-08-27 18:37:51 Re: missing locking in at least INSERT INTO view WITH CHECK
Previous Message Dean Rasheed 2015-08-27 18:19:35 Re: missing locking in at least INSERT INTO view WITH CHECK