mirror of
https://git.postgresql.org/git/postgresql.git
synced 2025-01-12 18:34:36 +08:00
Clarify old comment about qual_is_pushdown_safe's handling of subplans.
This comment glossed over the difference between initplans and subplans, but they are indeed different for our purposes here.
This commit is contained in:
parent
3848d21673
commit
801386af62
@ -2840,9 +2840,11 @@ targetIsInAllPartitionLists(TargetEntry *tle, Query *query)
|
||||
*
|
||||
* Conditions checked here:
|
||||
*
|
||||
* 1. The qual must not contain any subselects (mainly because I'm not sure
|
||||
* it will work correctly: sublinks will already have been transformed into
|
||||
* subplans in the qual, but not in the subquery).
|
||||
* 1. The qual must not contain any SubPlans (mainly because I'm not sure
|
||||
* it will work correctly: SubLinks will already have been transformed into
|
||||
* SubPlans in the qual, but not in the subquery). Note that SubLinks that
|
||||
* transform to initplans are safe, and will be accepted here because what
|
||||
* we'll see in the qual is just a Param referencing the initplan output.
|
||||
*
|
||||
* 2. If unsafeVolatile is set, the qual must not contain any volatile
|
||||
* functions.
|
||||
|
Loading…
Reference in New Issue
Block a user