On Tue, Jan 13, 2004 at 11:36:19PM -0500, Tom Lane wrote:
> Michael Adler <[EMAIL PROTECTED]> writes:
> > On many occasions, I've noticed that some PostgreSQL activity takes
> > far longer than it previously did and that disabling syslogd addresses
> > the symptoms.
> > ...
> > This evidence normally indicates a name resolution issue, but I'm not
> > sure how to test for that beyond using "hostname -v -i".
>
> I looked in Red Hat's bugzilla for similar issues, and found a mention
> that syslogd tries to reverse-lookup the address it gets each message
> from. A delay there could act as you describe. At least in recent RH
> releases, you can start syslogd with the "-x" switch to disable this
> lookup --- does that exist in Debian, and if so does it help?
There is no such option within Debian or the syslogd from freshmeat. Sounds nice,
though.
I was able to track down a name resolution issue. The "nameserver" in /etc/resolv.conf
pointed to a nonexistent host. This added ten second delays to telnetd logins and
netstat -a. This seemed to be the heart of the problem, but I'm getting some mixed
info from the "field" and I'm still following up.
Thanks,
Mike
---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match
