Michael Schout wrote:
> On Wed, May 17, 2000 at 11:59:15AM -0400, Tom Lane wrote:
> > Hmm. We were just discussing this a few weeks ago, when someone
> > suggested making the syslog option be the default and I wanted to
> > know if it was really robust enough for that. Seems it's not.
> Perhaps the maintainer of the binary RPMS on ftp.postgresql.org
> could rebuild with syslog logging turned off by default?
Set the pg_options -- ie, set syslog to 0, or set query to 0, if you
don't need query logging. There's no need to recompile, as the runtime
option sets things properly. I would prefer to not disable syslog when
it is working fine for those who have shorter queries. I will, however,
change the default pg_options with syslog set to 0 -- same effect, but
it still allows those with less difficult query-length requirements to
use the feature -- with the caveat that too long a query with query
logging on will crash out syslog.
So, I have two notices to add to the ramifordistat page, and to the
README.rpm..... I won't build a -2 release as yet, until we get the
actual query length of overflow (volunteers?) so that it can be
documented.
If you want to completely disable syslog on your own RPMS, feel free to
download the src.rpm, edit rpm-pgsql-7.0.patch to remove the USE_SYSLOG
define, and rebuild with rpm -ba. Then install the resulting RPMs. If
you wouldn't mind, change the release number so that no one gets
confused.
HTH
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
