Hmmmmm.... Very Interesting idea. I';l have to try that one.
One difference that may be an issue in other apps (not mine though) might be the inability to defer constraint checking
usingenum. Still, enum looks very appealing. And more portable, cleaner than parsing the values out of
pg_constraints.
Thanks Tom for that idea!
-----Original Message-----
From: Tom Lane [mailto:tgl@sss.pgh.pa.us]
Sent: Thursday, May 13, 2010 12:33 AM
To: Josh Kupershmidt
Cc: David Fetter; Gauthier, Dave; pgsql-general@postgresql.org
Subject: Re: [GENERAL] Pulling data from a constraint def
Josh Kupershmidt <schmiddy@gmail.com> writes:
> On Wed, May 12, 2010 at 12:58 AM, David Fetter <david@fetter.org> wrote:
>> If you've measured a performance issue for a table that tiny, it's a
>> bug that needs fixing in PostgreSQL. What measurements have you done
>> so far?
> Just for fun, I tried it out myself. Here are the times I got on my
> modest laptop:
> CHECK constraint:
> * 500k INSERTs: 3.8 seconds
> * 500k UPDATEs: 6.0 seconds
> Foreign Key:
> * 500k INSERTs: 18.7 seconds
> * 500k UPDATEs: 21.2 seconds
I'm surprised no one has yet suggested an ENUM type.
regards, tom lane
