Re: Misleading errors with column references in default expressions and partition bounds

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Misleading errors with column references in default expressions and partition bounds
Date: 2019-03-28 12:14:11
Message-ID: 20190328121411.GA2558@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Mar 27, 2019 at 12:13:16PM +0900, Michael Paquier wrote:
> ParseExprKind is an enum, so listing all the options without the
> default has the advantage to generate a warning if somebody adds a
> value. This way anybody changing this code will need to think about
> it.

A bit late, but committed without the case/default.

>> ... The value
>> is any variable-free expression (in particular, cross-references
>> to other columns in the current table are not allowed). Subqueries
>> are not allowed either.
>
> Okay, I think I see your point here. That sounds sensible.

And I have used this suggestion from Tom as well for the docs.
--
Michael

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Adrien NAYRAT 2019-03-28 12:14:39 Re: Log a sample of transactions
Previous Message Peter Eisentraut 2019-03-28 12:03:44 Re: Enable data checksums by default