Re: Nested loops are killing throughput - Mailing list pgsql-sql

From Tom Lane
Subject Re: Nested loops are killing throughput
Date
Msg-id 15725.1158693309@sss.pgh.pa.us
Whole thread Raw
In response to Re: Nested loops are killing throughput  (CG <cgg007@yahoo.com>)
Responses Re: Nested loops are killing throughput  (CG <cgg007@yahoo.com>)
Re: Nested loops are killing throughput  (CG <cgg007@yahoo.com>)
List pgsql-sql
CG <cgg007@yahoo.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


pgsql-sql by date:

Previous
From: "Henry Ortega"
Date:
Subject: Make Trigger run after completion of ENTIRE transaction
Next
From: CG
Date:
Subject: Re: Nested loops are killing throughput