Re: Further thoughts about warning for costly FK checks

From: Richard Huxton <dev(at)archonet(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Further thoughts about warning for costly FK checks
Date: 2004-03-14 11:30:27
Message-ID: 200403141130.27487.dev@archonet.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Meskes 2004-03-14 12:17:01 Re: ECPG - Remove need for "AT connection" when using threads
Previous Message Manfred Spraul 2004-03-14 11:15:46 Re: libpq thread safety