From: David Wheeler <david@kineticode.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: PostgreSQL Performance List <pgsql-performance@postgresql.org>
Subject: Re: Performance of DOMAINs
Date: Thu, 22 Jun 2006 11:11:36 -0700
Message-ID: <0878A4AB-925F-4CB8-BB75-53340599825D@kineticode.com> (raw)
In-Reply-To: <15919.1150920496@sss.pgh.pa.us>
References: <54D833BE-A58F-47B8-B070-2AEDC0802468@kineticode.com>
<15919.1150920496@sss.pgh.pa.us>
On Jun 21, 2006, at 13:08, Tom Lane wrote:
> There are some reports in the archives of particular usage patterns
> where they pretty much suck, because GetDomainConstraints() searches
> pg_constraint every time it's called. We do what we can to avoid
> calling that multiple times per query, but for something like a simple
> INSERT ... VALUES into a domain column, the setup overhead is still
> bad.
I assume that there's no domain thingy that you already have that
could cache it, eh?
Sorry, I ask this as someone who knows no C and less about
PostgreSQL's internals.
Best,
David
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-performance@postgresql.org
Cc: david@kineticode.com, tgl@sss.pgh.pa.us
Subject: Re: Performance of DOMAINs
In-Reply-To: <0878A4AB-925F-4CB8-BB75-53340599825D@kineticode.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