{"push_id":1388023654,"size":1,"distinct_size":1,"ref":"refs/heads/REL9_2_STABLE","head":"92b7b1058cf3ffb833085b953838af15add5ba29","before":"6653dbafd8526a63b91a8b3a020b1616d17977ba","commits":[{"sha":"92b7b1058cf3ffb833085b953838af15add5ba29","author":{"name":"Tom Lane","email":"9ca635a44fdf5aa326758d8d245579b9ae84653c@sss.pgh.pa.us"},"message":"Rationalize and document pltcl's handling of magic \".tupno\" array element.\n\nFor a very long time, pltcl's spi_exec and spi_execp commands have had\na behavior of storing the current row number as an element of output\narrays, but this was never documented.  Fix that.\n\nFor an equally long time, pltcl_trigger_handler had a behavior of silently\nignoring \".tupno\" as an output column name, evidently so that the result\nof spi_exec could be used directly as a trigger result tuple.  Not sure\nhow useful that really is, but in any case it's bad that it would break\nattempts to use \".tupno\" as an actual column name.  We can fix it by not\nchecking for \".tupno\" until after we check for a column name match.  This\ncomports with the effective behavior of spi_exec[p] that \".tupno\" is only\nmagic when you don't have an actual column named that.\n\nIn passing, wordsmith the description of returning modified tuples from\na pltcl trigger.\n\nNoted while working on Jim Nasby's patch to support composite results\nfrom pltcl.  The inability to return trigger tuples using \".tupno\" as\na column name is a bug, so back-patch to all supported branches.","distinct":true,"url":"https://api.github.com/repos/postgres/postgres/commits/92b7b1058cf3ffb833085b953838af15add5ba29"}]}
{"actor":{"display_login":"postgres-mirror"}}