Larry Rosenman <[EMAIL PROTECTED]> writes: > Looking some more, I found some other places that need a space (I > suspect...), so here is an updated patch. This seems like the wrong way to go about it, because anytime anyone changes any elog output anywhere, we'll risk another failure. If syslog can't cope with empty lines, I think the right fix is for the output-to-syslog routine to change the data just before sending --- then there is only one place to fix. See the syslog output routine in src/backend/utils/error/elog.c. regards, tom lane
- [HACKERS] syslog output from explain looks weird... Larry Rosenman
- Re: [HACKERS] syslog output from explain looks weir... Larry Rosenman
- Re: [HACKERS] syslog output from explain looks ... Larry Rosenman
- Re: [HACKERS] syslog output from explain lo... Tom Lane
- Re: [HACKERS] syslog output from explai... Larry Rosenman
- Re: [HACKERS] syslog output from e... Larry Rosenman
- Re: [HACKERS] syslog output fr... Bruce Momjian
- Re: [HACKERS] syslog outpu... Larry Rosenman
- Re: [HACKERS] syslog outpu... Bruce Momjian
- Re: [HACKERS] syslog outpu... Tatsuo Ishii
- [HACKERS] when will Postgr... xuyifeng
- Re: [HACKERS] when will Po... The Hermit Hacker
- Re: [HACKERS] syslog output from e... Bruce Momjian