pgsql: Remove ineffective check against dropped columns fromslot_getat - Mailing list pgsql-committers

From Andres Freund
Subject pgsql: Remove ineffective check against dropped columns fromslot_getat
Date
Msg-id E1gLIHR-0000Gj-Qs@gemulon.postgresql.org
Whole thread Raw
Responses Re: pgsql: Remove ineffective check against dropped columns from slot_getat
List pgsql-committers
Remove ineffective check against dropped columns from slot_getattr().

Before this commit slot_getattr() checked for dropped
columns (returning NULL in that case), but only after checking for
previously deformed columns. As slot_deform_tuple() does not contain
such a check, the check in slot_getattr() would often not have been
reached, depending on previous use of the slot.

These days locking and plan invalidation ought to ensure that dropped
columns are not accessed in query plans. Therefore this commit just
drops the insufficient check in slot_getattr().  It's possible that
we'll find some holes againt use of dropped columns, but if so, those
need to be addressed independent of slot_getattr(), as most accesses
don't go through that function anyway.

Author: Andres Freund
Discussion: https://postgr.es/m/20181107174403.zai7fedgcjoqx44p@alap3.anarazel.de

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/c670d0faace6184216c349a4cf830aa415c58068

Modified Files
--------------
src/backend/executor/execTuples.c | 11 -----------
1 file changed, 11 deletions(-)


pgsql-committers by date:

Previous
From: Andres Freund
Date:
Subject: pgsql: Don't require return slots for nodes without projection.
Next
From: Tom Lane
Date:
Subject: pgsql: Fix missing role dependencies for some schema and type ACLs.