From: CG <cgg007@yahoo.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-sql@postgresql.org
Subject: Re: Nested loops are killing throughput
Date: Tue, 19 Sep 2006 13:36:21 -0700 (PDT)
Message-ID: <20060919203621.25610.qmail@web37907.mail.mud.yahoo.com> (raw)
In-Reply-To: <15725.1158693309@sss.pgh.pa.us>
>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 ...)
It is the one from gborg. That's good to know.
So to fix, I should alter the supporting functions and set the ones that should not be VOLATILE to IMMUTABLE (newid() should be VOLATILE and that's about it) and set them to STRICT as well. I haven't had a problem with it crashing my backend in the three years we've been using it, but I'd rather not take any chances.
I know the hacker list has been batting back and forth the idea of a built-in UUID type. I'll be interested to see if you end up with a standard UUID type, a fixed field type with multiple generators for differing levels of paranoia, or the status quo.
CG
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: cgg007@yahoo.com, tgl@sss.pgh.pa.us
Subject: Re: Nested loops are killing throughput
In-Reply-To: <20060919203621.25610.qmail@web37907.mail.mud.yahoo.com>
* 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