Re: Instability in TRUNCATE regression test - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Instability in TRUNCATE regression test
Date
Msg-id 28313.1151517572@sss.pgh.pa.us
Whole thread Raw
In response to Re: Instability in TRUNCATE regression test  (Alvaro Herrera <alvherre@commandprompt.com>)
Responses Re: Instability in TRUNCATE regression test  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Alvaro Herrera <alvherre@commandprompt.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


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Instability in TRUNCATE regression test
Next
From: Bruce Momjian
Date:
Subject: Single Index Tuple Chain (SITC) method