To: "Dave Page" <dpage@vale-housing.co.uk>
Cc: Inoue@tpf.co.jp, ZeugswetterA@spardat.at, pgman@candle.pha.pa.us,
	pgsql-hackers@postgresql.org, pgsql-interfaces@postgresql.org
Subject: Re: Roadmap for FE/BE protocol redesign 
In-reply-to: <50073.80.177.99.193.1047549156.squirrel@ssl.vale-housing.co.uk> 
References: <03AF4E498C591348A42FC93DEA9661B8259D8D@mail.vale-housing.co.uk>
	<27130.1047484194@sss.pgh.pa.us> <3E702552.DA8A29A9@tpf.co.jp>
	<50073.80.177.99.193.1047549156.squirrel@ssl.vale-housing.co.uk>
Comments: In-reply-to "Dave Page" <dpage@vale-housing.co.uk>
	message dated "Thu, 13 Mar 2003 09:52:36 +0000"
Date: Thu, 13 Mar 2003 10:19:27 -0500
Message-ID: <4860.1047568767@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>

"Dave Page" <dpage@vale-housing.co.uk> writes:
> It's rumoured that Hiroshi Inoue once said:
>> Does looking up by the catalog keys take no cost ?

> Obviously there is cost, but doing a lookup only on demand, has got to be
> cheaper in the long run than including the entire column definition in the
> message whether it's wanted or not?

More to the point, the cost is paid by applications that want the
functionality, and not by those that don't.

It'd probably be reasonable for client libraries to maintain a cache
of column info, so that they only have to query the backend about a
particular column ID once per connection.  (This is one reason why
I want attrelid/attnum to be the info given on the wire: it's stable
enough to be used over a whole session to index such a cache.  Names
could not safely be used that way.)

			regards, tom lane