aboutsummaryrefslogtreecommitdiff
path: root/src/backend/executor/nodeBitmapOr.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2010-07-18 23:43:32 +0000
committerTom Lane <tgl@sss.pgh.pa.us>2010-07-18 23:43:32 +0000
commitcf5305f4066d827269b27f75af52dc2699d5426f (patch)
treec54dacee895414e91675d3abec695da184347486 /src/backend/executor/nodeBitmapOr.c
parentfba999cb2c8aeafc113b965682bcc9f9ce081c88 (diff)
downloadpostgresql-cf5305f4066d827269b27f75af52dc2699d5426f.tar.gz
postgresql-cf5305f4066d827269b27f75af52dc2699d5426f.zip
Remove unnecessary "Not safe to send CSV data" complaint from elog.c's fallback
path when CSV logging is configured but not yet operational. It's sufficient to send the message to stderr, as we were already doing, and the "Not safe" gripe has already confused at least two core members ... Backpatch to 9.0, but not further --- doesn't seem appropriate to change this behavior in stable branches.
Diffstat (limited to 'src/backend/executor/nodeBitmapOr.c')
0 files changed, 0 insertions, 0 deletions