From: | Dave Cramer <pg(at)fastcrypt(dot)com> |
---|---|
To: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: failed to re-find parent key |
Date: | 2004-01-13 23:21:48 |
Message-ID: | 1074036108.1149.92.camel@localhost.localdomain |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Sorry folks, this is a red-herring, my hack didn't have anything to do
with it. It occurs with or without the index. Question is was there a
bug between 7.4 and 7.4.1 which may have caused this?
Dave
On Tue, 2004-01-13 at 16:30, Dave Cramer wrote:
> I have hacked analyze.c to automatically create a unique index on the
> oid when a table is created and I am getting the failed to re-find
> parent key in pg_attribute_relid_attnam_index every 8 attempts to do the
> following
>
> select * from foo into temp a;
> drop table a;
>
> Currently analyze does not create the oid index on the select into.
>
> I realize this is beyond the realm of supported code, but can anyone
> tell me what's going on or a better way to fix it.
>
> BTW, the real problem is that select * from foo where oid=? doesn't use
> an index scan.
>
> Dave
--
Dave Cramer
519 939 0336
ICQ # 1467551
From | Date | Subject | |
---|---|---|---|
Next Message | Claudio Natoli | 2004-01-13 23:35:41 | Re: LWLock/ShmemIndex startup question |
Previous Message | Dave Cramer | 2004-01-13 21:30:48 | failed to re-find parent key |