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

Re: Instability in TRUNCATE regression test

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
Cc: pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: Instability in TRUNCATE regression test
Date: 2006-06-28 17:59:32
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:
> Tom Lane wrote:
>> One thing I was toying with was to add an index to pg_constraint on,
>> say, (confrelid, conrelid), and to replace the existing seqscans for FK
>> constraints with scans using this index.

> I think there is more than one place that would benefit from such an
> index.  Probably turn into a syscache as well?

Yeah, that was in the back of my mind too, but I haven't looked through
the code to see.  A syscache wouldn't work because it's not a unique key.

			regards, tom lane

In response to


pgsql-hackers by date

Next:From: Jim C. NasbyDate: 2006-06-28 18:12:17
Subject: Re: Fixed length datatypes. WAS [GENERAL] UUID's as
Previous:From: Tom LaneDate: 2006-06-28 17:58:13
Subject: Re: Instability in TRUNCATE regression test

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