Fix bug in handling of dropped columns in pltcl triggers - Mailing list pgsql-hackers

From Jim Nasby
Subject Fix bug in handling of dropped columns in pltcl triggers
Date
Msg-id b2de8258-c4c0-1cb8-7b97-e8538e5c975c@BlueTreble.com
Whole thread Raw
Responses Re: Fix bug in handling of dropped columns in pltcl triggers  (Michael Paquier <michael.paquier@gmail.com>)
List pgsql-hackers
While reviewing code coverage in pltcl, I uncovered a bug in trigger
function return handling. If you returned the munged name of a dropped
column, that would silently be ignored. It would be unusual to hit this,
since dropped columns end up with names like
".......pg.dropped.2.......", but since that's still a legitimate name
for a column silently ignoring it seems rather bogus.

Work sponsored by FlightAware.

https://github.com/postgres/postgres/compare/master...decibel:tcl_dropped
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com
855-TREBLE2 (855-873-2532)   mobile: 512-569-9461

Attachment

pgsql-hackers by date:

Previous
From: Peter Geoghegan
Date:
Subject: Re: Unsafe use of relation->rd_options without checking its type
Next
From: Amit Kapila
Date:
Subject: Re: Speed up Clog Access by increasing CLOG buffers