Re: Roadmap for FE/BE protocol redesign

From: Greg Stark <gsstark(at)mit(dot)edu>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Roadmap for FE/BE protocol redesign
Date: 2003-03-14 15:22:19
Message-ID: 87r89ac6s4.fsf@stark.dyndns.tv
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-interfaces


So, just to throw out a wild idea: If you're talking about making large
changes to the on-the-wire protocol. Have you considered using an existing
database protocol? This would avoid having to reinvent the wheel every time
postgres implements a new feature like prepared queries, bind arrays, or
metadata information.

There is a free implementation of the TDS (Tabular DataStream) protocol used
by Sybase and MSSQL. I don't know how much of it would be interesting for
postgres and how much is Sybase/MSSQL-specific.

It would be pretty neat if postgres could use precisely the same on-the-wire
protocol as other major databases, just requiring a separate high level driver
to interpret the semantic meaning of the data.

At the very least it sounds like interesting to do a compare and contrast as
far as understanding what advantages the features TDS has have and what
disadvantages, before postgres possibly misses good ideas or makes the same
mistakes.

--
greg

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2003-03-14 15:33:05 Re: Upgrading the backend's error-message infrastructure
Previous Message Zeugswetter Andreas SB SD 2003-03-14 15:19:45 Re: Roadmap for FE/BE protocol redesign

Browse pgsql-interfaces by date

  From Date Subject
Next Message Tom Lane 2003-03-14 15:33:05 Re: Upgrading the backend's error-message infrastructure
Previous Message Darko Prenosil 2003-03-14 12:29:32 Re: Upgrading the backend's error-message infrastructure