Thanks! RFC5426 appears to require a minimum of 480 octets on IP
V4. I don't know when that went into effect, but I have no idea
whether it's implemented to spec on all the platforms postgres
supports. PG_SYSLOG_LIMIT is set to 128.
On Wed, 09 Feb 2011 12:09:06 -0500 Tom Lane <tgl@sss.pgh.pa.us>
wrote:
>l1@nym.hush.com writes:
>> The problem I'm running into is that lines are getting broken
>up.
>
>Yup, that's intentional.
>
>> This causes problems with some other log-scanners I use. Is the
>
>> problem postgres or syslog? I know syslog has a maximum message
>
>> size, but it's a lot longer than what Postgres seems to use.
>
>syslog's limit is platform-dependent, and at least on some
>platforms
>it's pretty darn small. If you know for sure what your platform
>can tolerate, you can alter PG_SYSLOG_LIMIT in
>src/backend/utils/error/elog.c. There's no way to change it
>without a recompile.
>
> regards, tom lane
