On 2017/07/26 16:58, Amit Langote wrote:
> Rajkumar Raghuwanshi reported [1] on the "UPDATE partition key" thread
> that whole-row vars don't play nicely with partitioned table operations.
>
> For example, when used to convert WITH CHECK OPTION constraint expressions
> and RETURNING target list expressions, it will error out if the
> expressions contained whole-row vars. That's a bug, because whole-row
> vars are legal in those expressions. I think the decision to output error
> upon encountering a whole-row in the input expression was based on the
> assumption that it will only ever be used to convert partition constraint
> expressions, which cannot contain those. So, we can relax that
> requirement so that its other users are not bitten by it.
>
> Attached fixes that.
Attached a revised version of the patch.
Updated patch moves the if (found_whole_row) elog(ERROR) bit in
map_partition_varattnos to the callers. Only the callers know if
whole-row vars are not expected in the expression it's getting converted
from map_partition_varattnos. Given the current message text (mentioning
"partition key"), it didn't seem appropriate to have the elog inside this
function, since it's callable from places where it wouldn't make sense.
Thanks,
Amit
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers