From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | pgsql-committers(at)postgresql(dot)org |
Subject: | pgsql: Use ExecPrepareExpr in place of ExecPrepareCheck where appropria |
Date: | 2017-03-26 22:14:08 |
Message-ID: | E1csGQK-0004YC-EI@gemulon.postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
Use ExecPrepareExpr in place of ExecPrepareCheck where appropriate.
Change one more place where ExecInitCheck/ExecPrepareCheck's insistence
on getting implicit-AND-format quals wasn't really helpful, because the
caller had to do make_ands_implicit() for no reason that it cared about.
Using ExecPrepareExpr directly simplifies the code and saves cycles.
The only remaining use of these functions is to process
resultRelInfo->ri_PartitionCheck quals. However, implicit-AND format
does seem to be what we want for that, so leave it alone.
Branch
------
master
Details
-------
http://git.postgresql.org/pg/commitdiff/9b95f2fa1e2684fa209a3594db2254b8841bf380
Modified Files
--------------
src/backend/catalog/partition.c | 6 +++++-
src/backend/commands/tablecmds.c | 22 ++++++++++------------
2 files changed, 15 insertions(+), 13 deletions(-)
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2017-03-26 22:32:26 | pgsql: Fix cpluspluscheck warning |
Previous Message | Tom Lane | 2017-03-26 21:44:41 | pgsql: Fix typos in logical replication support for initial data copy. |