summaryrefslogtreecommitdiff
path: root/src/backend/access/gist/gistxlog.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2017-12-31 17:20:17 -0500
committerTom Lane <tgl@sss.pgh.pa.us>2017-12-31 17:20:17 -0500
commit3e724aac74e8325fe48dac8a30c2a7974eff7a14 (patch)
tree8d75c30dc70c33826b2de72d929a07bfe09617c0 /src/backend/access/gist/gistxlog.c
parentdd2243f2ade43bcad8e615e6cf4286be250e374a (diff)
downloadpostgresql-3e724aac74e8325fe48dac8a30c2a7974eff7a14.tar.gz
Merge coding of return/exit/continue cases in plpgsql's loop statements.
plpgsql's five different loop control statements contained three distinct implementations of the same (or what ought to be the same, at least) logic for handling return/exit/continue result codes from their child statements. At best, that's trouble waiting to happen, and there seems no very good reason for the coding to be so different. Refactor so that all the common logic is expressed in a single macro. Discussion: https://postgr.es/m/26314.1514670401@sss.pgh.pa.us
Diffstat (limited to 'src/backend/access/gist/gistxlog.c')
0 files changed, 0 insertions, 0 deletions