aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/gist/gistscan.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2007-07-21 22:12:11 +0000
committerTom Lane <tgl@sss.pgh.pa.us>2007-07-21 22:12:11 +0000
commit6537d9ce6af90704665182e93a26f82ef315b5ae (patch)
tree26c4baba5a0afca49903b79ca585eb0259b9ab44 /src/backend/access/gist/gistscan.c
parent85506ffbd51e15dffbd307e4d1060cfffb24c9e0 (diff)
downloadpostgresql-6537d9ce6af90704665182e93a26f82ef315b5ae.tar.gz
postgresql-6537d9ce6af90704665182e93a26f82ef315b5ae.zip
Fix elog.c to avoid infinite recursion (leading to backend crash) when
log_min_error_statement is active and there is some problem in logging the current query string; for example, that it's too long to include in the log message without running out of memory. This problem has existed since the log_min_error_statement feature was introduced. No doubt the reason it wasn't detected long ago is that 8.2 is the first release that defaults log_min_error_statement to less than PANIC level. Per report from Bill Moran.
Diffstat (limited to 'src/backend/access/gist/gistscan.c')
0 files changed, 0 insertions, 0 deletions