On Sat, Apr 23, 2011 at 2:57 PM, Gianni Ciolli
gianni.cio...@2ndquadrant.it wrote:
* avg_usec denotes the average time in microseconds required by each
NOTIFY statement.
h2. Test 1 - PostgreSQL HEAD
n | m | iter | avg_usec
---+---+--+--
10 | 1 | 10 |
On Sat, Apr 23, 2011 at 8:44 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Gianni Ciolli gianni.cio...@2ndquadrant.it writes:
[ proposes lobotomization of duplicate-elimination behavior in NOTIFY ]
I think this change is likely to be penny-wise and pound-foolish.
The reason the duplicate check is in
Hi,
while measuring NOTIFY execution time, I noticed a significant
performance drop.
Please find a patch attached, together with some tests; more details
are shown below.
Best regards,
Dr. Gianni Ciolli - 2ndQuadrant Italia
PostgreSQL Training, Services and Support
gianni.cio...@2ndquadrant.it
Gianni Ciolli gianni.cio...@2ndquadrant.it writes:
[ proposes lobotomization of duplicate-elimination behavior in NOTIFY ]
I think this change is likely to be penny-wise and pound-foolish.
The reason the duplicate check is in there is that things like triggers
may just do NOTIFY
