From: Tom Lane <tgl@sss.pgh.pa.us>
To: Joel Stevenson <joelstevenson@mac.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: LISTEN / NOTIFY performance in 8.3
Date: Mon, 25 Feb 2008 13:13:14 -0500
Message-ID: <29568.1203963194@sss.pgh.pa.us> (raw)
In-Reply-To: <p0624080ec3e8ade18d73@[192.168.0.9]>
References: <p0624080ec3e8ade18d73@[192.168.0.9]>
Joel Stevenson <joelstevenson@mac.com> writes:
>> Also, it might be worth enabling log_lock_waits to see if the slow
>> notifies are due to having to wait on some lock or other.
> Turning on log_lock_waits shows that there is a lot of waiting for
> locks on the pg_listener table ala:
Interesting. The LISTEN/NOTIFY mechanism itself takes ExclusiveLock
on pg_listener, but never for very long at a time (assuming pg_listener
doesn't get horribly bloated, which we know isn't happening for you).
Another thought that comes to mind is that maybe the delays you see
come from these lock acquisitions getting blocked behind autovacuums of
pg_listener. I did not see that while trying to replicate your problem,
but maybe the issue requires more update load on pg_listener than the
test script can create by itself, or maybe some nondefault autovacuum
setting is needed --- what are you using?
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 using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: tgl@sss.pgh.pa.us, joelstevenson@mac.com
Subject: Re: LISTEN / NOTIFY performance in 8.3
In-Reply-To: <29568.1203963194@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