Re: Roadmap for FE/BE protocol redesign

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk>
Cc: Inoue(at)tpf(dot)co(dot)jp, ZeugswetterA(at)spardat(dot)at, pgman(at)candle(dot)pha(dot)pa(dot)us, pgsql-hackers(at)postgresql(dot)org, pgsql-interfaces(at)postgresql(dot)org
Subject: Re: Roadmap for FE/BE protocol redesign
Date: 2003-03-13 15:19:27
Message-ID: 4860.1047568767@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-interfaces

"Dave Page" <dpage(at)vale-housing(dot)co(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Greg Stark 2003-03-13 15:29:03 Re: Roadmap for FE/BE protocol redesign
Previous Message Manfred Koizar 2003-03-13 15:16:29 Re: [SQL] What's wrong with this group by clause?

Browse pgsql-interfaces by date

  From Date Subject
Next Message Chris Jewell 2003-03-13 15:28:20 Seg fault on completing query
Previous Message Hiroshi Inoue 2003-03-13 15:05:22 Re: Roadmap for FE/BE protocol redesign