From: Tom Lane <tgl@sss.pgh.pa.us>
To: Michael Adler <adler@pobox.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: vacuum slowed by syslogd
Date: Tue, 13 Jan 2004 23:36:19 -0500
Message-ID: <29721.1074054979@sss.pgh.pa.us> (raw)
In-Reply-To: <20040114031030.GA18188@pobox.com>
References: <20040114031030.GA18188@pobox.com>
Michael Adler <adler@pobox.com> 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?
I would expect any comparable resolution delays on the client side to
occur only once when a backend is started, not once per message, since
we only openlog() once per backend. So a delay on the syslogd side
seems a likely theory.
Something else you could do to investigate is to test whether syslogd
can log messages from other clients during these 10-second delays.
If it's hung trying to resolve a name, presumably messages from other
clients would get delayed too.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, adler@pobox.com
Subject: Re: vacuum slowed by syslogd
In-Reply-To: <29721.1074054979@sss.pgh.pa.us>
References: <20040114031030.GA18188@pobox.com> <29721.1074054979@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox