pg.ddx.io  pgsql-interfaces@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Hannu Krosing <hannu@tm.ee>
To: Greg Stark <gsstark@mit.edu>
Cc: Marc G. Fournier <scrappy@hub.org>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-hackers@postgresql.org
Cc: pgsql-interfaces@postgresql.org
Subject: Re: [INTERFACES] Roadmap for FE/BE protocol redesign
Date: 13 Mar 2003 08:29:19 +0200
Message-ID: <1047536959.3223.5.camel@fuji.krosing.net> (raw)
In-Reply-To: <87zno1gofs.fsf@stark.dyndns.tv>
References: <19041.1047322279@sss.pgh.pa.us>
	<20030311211526.H72192@hub.org>
	<87zno1gofs.fsf@stark.dyndns.tv>

Greg Stark kirjutas K, 12.03.2003 kell 07:10:
> "Marc G. Fournier" <scrappy@hub.org> writes:
> 
> > Personally ... as long as a v8.x client can talk to a v7.x backend, you
> > have my vote ... I'm more apt to upgrade my clients before my servers
> > anyway ...
> 
> Surely that's not true for a production environment. You have one database but
> potentially dozens of various programs around that access it. The main
> application, some backend scripts for batch jobs, your backup process, your
> monitoring systems... Not all of these are necessarily on the same machine.

For more radical protocol changes a viable approach could be "protocol
proxies", i.e. set up a _separate_ daemon which listens on a separate
port and translates v7.x wire protocol to v8.x of the database proper.

Then those needing it can keep it around and those who need it not don't
get the overhead. It could also be maintained by inerested parties long
after being dropped by core developers.

> It's upgrading the database that's likely to be the driving motivation for new
> sql or storage features. People usually don't get excited about upgrading the
> client libraries :)

But our SQL itself is slowly drifting towards ANSI/ISO compliance and
that has often brought subtle changes that break _applications_. It is
not a big issue to changes libraries if you have to change the
application anyway.

-----------------
Hannu




view thread (133+ messages)  latest in thread

Message-ID: <1047536959.3223.5.camel@fuji.krosing.net>
Permalink:  ../1047536959.3223.5.camel@fuji.krosing.net/
Also on:    postgresql.org/message-id/1047536959.3223.5.camel@fuji.krosing.net

 · 

reply

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: hannu@tm.ee, gsstark@mit.edu, scrappy@hub.org, tgl@sss.pgh.pa.us, pgsql-hackers@postgresql.org
  Subject: Re: [INTERFACES] Roadmap for FE/BE protocol redesign
  In-Reply-To: <1047536959.3223.5.camel@fuji.krosing.net>

* 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