Re: Roadmap for FE/BE protocol redesign

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: Dave Page <dpage(at)vale-housing(dot)co(dot)uk>, PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Roadmap for FE/BE protocol redesign
Date: 2003-03-12 18:21:51
Message-ID: 28044.1047493311@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> What you need is an updateable cursor on the server side. It has all the
> facilities you need, including standardized ways to find out the
> updatability metadata. Please concentrate on that and do not attempt to
> clutter the wire protocol with data that will not withstand a throrough
> investigation of semantics.

So are you voting against adding any attribute-ID info to
RowDescription? While I'm not that thrilled with it myself, it seems
relatively harmless as long as we can keep the overhead down. I'm
okay with attrelid/attnum, but would gripe about including more than that.

You're probably right that updatable cursors would be a nicer solution
in the long run, but I don't really see that happening in the next
release or two.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Merlin Moncure 2003-03-12 18:31:48 Re: Roadmap for FE/BE protocol redesign
Previous Message Rod Taylor 2003-03-12 17:59:10 Re: Case insensitivity, and option?