From: Bruce Badger <bruce_badger@badgerse.com>
To: pgsql-hackers@postgresql.org
To: pgsql-interfaces@postgresql.org
Subject: Re: [INTERFACES] Roadmap for FE/BE protocol redesign
Date: 11 Mar 2003 08:41:10 +1100
Message-ID: <1047332470.10722.6.camel@alice> (raw)
In-Reply-To: <19483.1047325975@sss.pgh.pa.us>
References: <19041.1047322279@sss.pgh.pa.us>
<1047324016.99075.31.camel@jester>
<19294.1047324622@sss.pgh.pa.us>
<1047325296.99075.35.camel@jester>
<19483.1047325975@sss.pgh.pa.us>
On Tue, 2003-03-11 at 06:52, Tom Lane wrote:
> Rod Taylor <rbt@rbt.ca> writes:
> >> We already have that: you send a startup packet with a version less than
> >> the latest, and the backend speaks that version to you.
>
> > Yes, but that requires you know the backend is less than the latest.
>
> As opposed to knowing what? You send the version number you wish to speak;
> either the backend can handle it, or not.
If the backend can not handle the version I request, but can handle a
prior version, I'd like to know. I am planning on having handlers for
multiple protocol versions in the same memory space (I'm using
Smalltalk, BTW) so that one application can talk to various databases of
various vintages.
I suppose that the client can just keep retrying the connection with
different versions until it gets a match, though.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-interfaces@postgresql.org
Cc: bruce_badger@badgerse.com, pgsql-hackers@postgresql.org
Subject: Re: [INTERFACES] Roadmap for FE/BE protocol redesign
In-Reply-To: <1047332470.10722.6.camel@alice>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox