Skip site navigation (1) Skip section navigation (2)

Re: Tuning single row operations

From: "Simon Riggs" <simon(at)2ndquadrant(dot)com>
To: "Matthew O'Connor" <matthew(at)zeut(dot)net>
Cc: "Richard Huxton" <dev(at)archonet(dot)com>,<pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Tuning single row operations
Date: 2006-12-21 14:56:30
Message-ID: 1166712990.3783.58.camel@silverbirch.site (view raw or flat)
Thread:
Lists: pgsql-hackers
On Thu, 2006-12-21 at 09:36 -0500, Matthew O'Connor wrote:
> Richard Huxton wrote:
> > Simon Riggs wrote:
> >> - improve RI check perf by caching small, static tables in each backend
> >> - apply index filter conditions on index scan to avoid heap lookup
> > 
> > For fkey checks against a basically static table could you get away with 
> > just checking the index and not the table?
> 
> I'm not sure that would fly, there is always the possibility it could 
> change, I think the ENUMs patch will solve this performance problem.

Not using SQL Standard syntax it won't. 

I'd be happier if it worked with DOMAINs and happier still if we can get
it to optimise just bare datatypes. My objective is to tune a database
without needing to reload any of the tables and to ensure that RI is
effective in both directions (from referencing and referenced tables).

Perhaps there's a way to make that happen...

-- 
  Simon Riggs             
  EnterpriseDB   http://www.enterprisedb.com



In response to

Responses

pgsql-hackers by date

Next:From: Simon RiggsDate: 2006-12-21 15:04:43
Subject: Re: Interface for pg_autovacuum
Previous:From: Zeugswetter Andreas ADI SDDate: 2006-12-21 14:39:07
Subject: Re: column ordering, was Re: [PATCHES] Enums patch v2

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group