On 11/9/18 4:51 PM, Adam Berlin wrote:
> As a newcomer to this patch, when I read this example:
>
> COPY table_name WHEN (some_condition)
>
> .. I expect COPY to only be run when the condition is true, and I do
not expect the WHEN clause to filter rows. I'm curious what you think about:
>
Hmmm. Currently we have WHEN clause in three places:
1) triggers, where it specifies arbitrary expression on rows,
determining whether the trigger should be invoked at all
2) event triggers, where it does about the same thing as for regular
triggers, but only expressions "column IN (...)" are allowed
3) CASE WHEN ... THEN ...
I'd say 3 is rather unrelated to this discussion, and 1+2 seem to
support you objection to using WHEN for COPY, as it kinda specifies
whether the command itself should be executed.
> COPY table_name WHERE (some_condition)
>
> Users should already be familiar with the idea that WHERE performs a filter.
>
So, what about using FILTER here? We already use it for aggregates when
filtering rows to process.
That being said, I have no strong feelings either way. I'd be OK with
both WHEN and WHERE.
regards
--
Tomas Vondra http://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
