Re: [idea] a copied relkind in pg_attribute - Mailing list pgsql-hackers

From Jaime Casanova
Subject Re: [idea] a copied relkind in pg_attribute
Date
Msg-id 3073cc9b0812240812ta5e44fu9d62ee5b4fb835ac@mail.gmail.com
Whole thread Raw
In response to [idea] a copied relkind in pg_attribute  (KaiGai Kohei <kaigai@kaigai.gr.jp>)
Responses Re: [idea] a copied relkind in pg_attribute  (KaiGai Kohei <kaigai@ak.jp.nec.com>)
List pgsql-hackers
On Wed, Dec 24, 2008 at 6:50 AM, KaiGai Kohei <kaigai@kaigai.gr.jp> wrote:
>
> The current implementation need to lookup RELOID system cache to
> identify the relkind of the relation, because pg_attribtue does
> not have any information about "relkind". However, I also think
> it is not an ideal implementation, even if its frequency is enough
> small.
>

but you still can do it, right?
there are any other advantages, like something you can't do now?
if not, i think you need to probe that there will be any benefit in
speed and that is significant otherwise this seems like premature
optimization and that AFAIR is the root of all evil :)

--
Atentamente,
Jaime Casanova
Soporte y capacitación de PostgreSQL
Asesoría y desarrollo de sistemas
Guayaquil - Ecuador
Cel. +59387171157


pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Re: Hot standby and b-tree killed items
Next
From: Tom Lane
Date:
Subject: Re: generic reloptions improvement