pgsql: Fix incorrect logic for caching ResultRelInfos for triggers

2025-10-25 Thread David Rowley
Fix incorrect logic for caching ResultRelInfos for triggers When dealing with ResultRelInfos for partitions, there are cases where there are mixed requirements for the ri_RootResultRelInfo. There are cases when the partition itself requires a NULL ri_RootResultRelInfo and in the same query, the s

pgsql: Fix incorrect logic for caching ResultRelInfos for triggers

2025-10-25 Thread David Rowley
Fix incorrect logic for caching ResultRelInfos for triggers When dealing with ResultRelInfos for partitions, there are cases where there are mixed requirements for the ri_RootResultRelInfo. There are cases when the partition itself requires a NULL ri_RootResultRelInfo and in the same query, the s

pgsql: Fix incorrect logic for caching ResultRelInfos for triggers

2025-10-25 Thread David Rowley
Fix incorrect logic for caching ResultRelInfos for triggers When dealing with ResultRelInfos for partitions, there are cases where there are mixed requirements for the ri_RootResultRelInfo. There are cases when the partition itself requires a NULL ri_RootResultRelInfo and in the same query, the s

pgsql: Fix incorrect logic for caching ResultRelInfos for triggers

2025-10-25 Thread David Rowley
Fix incorrect logic for caching ResultRelInfos for triggers When dealing with ResultRelInfos for partitions, there are cases where there are mixed requirements for the ri_RootResultRelInfo. There are cases when the partition itself requires a NULL ri_RootResultRelInfo and in the same query, the s

pgsql: Fix incorrect logic for caching ResultRelInfos for triggers

2025-10-25 Thread David Rowley
Fix incorrect logic for caching ResultRelInfos for triggers When dealing with ResultRelInfos for partitions, there are cases where there are mixed requirements for the ri_RootResultRelInfo. There are cases when the partition itself requires a NULL ri_RootResultRelInfo and in the same query, the s