Re: Further thoughts about warning for costly FK checks - Mailing list pgsql-hackers

From Richard Huxton
Subject Re: Further thoughts about warning for costly FK checks
Date
Msg-id 200403141130.27487.dev@archonet.com
Whole thread Raw
In response to Re: Further thoughts about warning for costly FK checks  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Sunday 14 March 2004 00:16, Tom Lane wrote:

> > Call me crazy, but maybe we have to throw a message for primary
> > key lookups on foreign key tables without indexes.  I hate to throw a
> > message on update/delete rather than create table, but I don't see
> > another way.
>
> I don't think that will fly.  It's too noisy/repetitive, and it's
> complaining at the wrong time (in production rather than when you're
> setting up the DB schema).  Imagine how annoying it would be to get
> such warnings if you were a user without the privileges needed to create
> the requested index.

Maybe there should be a separate "pg_advisor" tool that you can run against a 
database and which looks for "oddities". Something pluggable so people can 
add tests simply.

--  Richard Huxton Archonet Ltd


pgsql-hackers by date:

Previous
From: Manfred Spraul
Date:
Subject: Re: libpq thread safety
Next
From: Andrew Dunstan
Date:
Subject: listening addresses