Re: Nested loops are killing throughput

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: CG <cgg007(at)yahoo(dot)com>
Cc: pgsql-sql(at)postgresql(dot)org
Subject: Re: Nested loops are killing throughput
Date: 2006-09-19 19:15:09
Message-ID: 15725.1158693309@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-sql

CG <cgg007(at)yahoo(dot)com> writes:
>> If packet_status is large, that seems like a perfectly reasonable plan
>> to me. If not ... what data type is packet_uuid? Is its equality op
>> marked mergeable or hashable?

> It is of type uniqueidentifier ...

Is that the one off gborg? It's broken because the equality function is
marked volatile, and so the planner is afraid to try to use it for
merging or hashing. (It's also not marked strict, which means you can
trivially crash the backend by passing it a null ...)

regards, tom lane

In response to

Responses

Browse pgsql-sql by date

  From Date Subject
Next Message CG 2006-09-19 20:36:21 Re: Nested loops are killing throughput
Previous Message Henry Ortega 2006-09-19 19:00:52 Make Trigger run after completion of ENTIRE transaction