From: Tom Lane <tgl@sss.pgh.pa.us>
To: CG <cgg007@yahoo.com>
Cc: pgsql-sql@postgresql.org
Subject: Re: Nested loops are killing throughput
Date: Tue, 19 Sep 2006 15:15:09 -0400
Message-ID: <15725.1158693309@sss.pgh.pa.us> (raw)
In-Reply-To: <20060919185913.21542.qmail@web37908.mail.mud.yahoo.com>
References: <20060919185913.21542.qmail@web37908.mail.mud.yahoo.com>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: tgl@sss.pgh.pa.us, cgg007@yahoo.com
Subject: Re: Nested loops are killing throughput
In-Reply-To: <15725.1158693309@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox