]> granicus.if.org Git - postgresql/commit
Adjust the behavior of the PQExpBuffer code to make it have well-defined
authorTom Lane <tgl@sss.pgh.pa.us>
Wed, 26 Nov 2008 00:26:23 +0000 (00:26 +0000)
committerTom Lane <tgl@sss.pgh.pa.us>
Wed, 26 Nov 2008 00:26:23 +0000 (00:26 +0000)
commit739259d62e6f96afecea1470c69004631d7aa264
treee1e9f58dda5d66578f0356bf7593fec8acbaa849
parent8a10096440eaf1f5b918aebec71c2d5ad2687fe6
Adjust the behavior of the PQExpBuffer code to make it have well-defined
results (ie, an empty "broken" buffer) if memory overrun occurs anywhere
along the way to filling the buffer.  The previous coding would just silently
discard portions of the intended buffer contents, as exhibited in trouble
report from Sam Mason.  Also, tweak psql's main loop to correctly detect
and report such overruns.  There's probably much more that should be done
in this line, but this is a start.
src/bin/psql/input.c
src/bin/psql/mainloop.c
src/bin/psql/psqlscan.l
src/interfaces/libpq/fe-connect.c
src/interfaces/libpq/pqexpbuffer.c
src/interfaces/libpq/pqexpbuffer.h