From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Steve King <steve(dot)king(at)ecmsys(dot)co(dot)uk> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Bad rules |
Date: | 2002-10-04 14:48:10 |
Message-ID: | 20734.1033742890@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Steve King <steve(dot)king(at)ecmsys(dot)co(dot)uk> writes:
> I am using postgres 7.2, and have rule on a table which causes a notify if
> an insert/update/delete is performed on the table.
> The table is very very small.
> When performing a simple (very simple) update on the table this takes about
> 3 secs, when I remove the rule it is virtually instantaneous.
> The rest of the database seems to perform fine, have you any ideas or come
> across this before??
Let's see the rule exactly? NOTIFY per se is not slow in my experience.
(One thing to ask: have you done a VACUUM FULL on pg_listener in recent
memory? Heavy use of LISTEN/NOTIFY does tend to bloat that table if you
don't keep after it with VACUUM.)
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Manfred Koizar | 2002-10-04 15:13:32 | Re: Correlation in cost_index() |
Previous Message | Hans-Jürgen Schönig | 2002-10-04 14:40:37 | Re: Threaded Sorting |