Skip site navigation (1) Skip section navigation (2)

Re: Hash Anti Join performance degradation

From: panam <panam(at)gmx(dot)net>
To: pgsql-performance(at)postgresql(dot)org
Subject: Re: Hash Anti Join performance degradation
Date: 2011-05-26 18:04:35
Message-ID: 1306433075215-4429475.post@n5.nabble.com (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-performance
Sorry,

SELECT MAX(e.id) FROM event_message e WHERE e.box_id = id

as posted previously should actually read

SELECT max(m1.id) FROM message m1 WHERE m1.box_id = b.id)

so I tried this already.

Regards,
panam




--
View this message in context: http://postgresql.1045698.n5.nabble.com/Hash-Anti-Join-performance-degradation-tp4420974p4429475.html
Sent from the PostgreSQL - performance mailing list archive at Nabble.com.

In response to

pgsql-performance by date

Next:From: Cédric VillemainDate: 2011-05-26 18:13:22
Subject: Re: Hash Anti Join performance degradation
Previous:From: Kevin GrittnerDate: 2011-05-26 17:45:32
Subject: Re: The shared buffers challenge

pgsql-hackers by date

Next:From: Kevin GrittnerDate: 2011-05-26 18:05:55
Subject: Re: [ADMIN] pg_class reltuples/relpages not updated by autovacuum/vacuum
Previous:From: Robert HaasDate: 2011-05-26 17:55:53
Subject: Re: Pre-alloc ListCell's optimization

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group