Tom Lane 8a2e323f20 Handle mixed returnable and non-returnable columns better in IOS. ... We can revert the code changes of commit b5febc1d1 now, because commit 9a3ddeb51 installed a real solution for the difficulty that b5febc1d1 just dodged, namely that the planner might pick the wrong one of several index columns nominally containing the same value. It only matters which one we pick if we pick one that's not returnable, and that mistake is now foreclosed. Although both of the aforementioned commits were back-patched, I don't feel a need to take any risk by back-patching this one. The cases that it improves are very corner-ish. Discussion: https://postgr.es/m/3179992.1641150853@sss.pgh.pa.us		2022-01-03 16:12:11 -05:00
..
bit.sql
bool.sql
bytea.sql
cash.sql
char.sql
cidr.sql
date.sql
enum.sql
float4.sql
float8.sql
inet.sql	Handle mixed returnable and non-returnable columns better in IOS.	2022-01-03 16:12:11 -05:00
init.sql
int2.sql
int4.sql
int8.sql
interval.sql
macaddr8.sql
macaddr.sql
not_equal.sql
numeric.sql
oid.sql
text.sql
time.sql
timestamp.sql
timestamptz.sql
timetz.sql
uuid.sql
varbit.sql
varchar.sql