| From: | The Hermit Hacker <scrappy(at)hub(dot)org> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Magnus Hagander <mha(at)sollentuna(dot)net>, pgsql-hackers(at)postgreSQL(dot)org |
| Subject: | Re: [HACKERS] RE: [INTERFACES] Re: SSL patch |
| Date: | 1999-07-24 17:06:07 |
| Message-ID: | Pine.BSF.4.05.9907241403560.55528-100000@thelab.hub.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sat, 24 Jul 1999, Tom Lane wrote:
> Magnus Hagander <mha(at)sollentuna(dot)net> writes:
> > Just to clearify: the SSL-enabled server still accepts 6.6 clients that are
> > compiled without SSL support, but it will not accept from 6.5 clients, as it
> > is now.
>
> Right. My feeling is that we must make it possible for a 6.6 server to
> accept connections from 6.5 (and earlier) clients, or the upgrade will
> be too painful at large sites.
But, we've had protocol changes before that breaks backward
compatibility...why is this all of a sudden a problem? As long as this is
a "known" issue for an upgrade (something for the 'migrating to...'
section of the HISTORY file), I personally see no reason why the protocol
can't mature/change...
Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: scrappy(at)hub(dot)org secondary: scrappy(at){freebsd|postgresql}.org
| From | Date | Subject | |
|---|---|---|---|
| Next Message | The Hermit Hacker | 1999-07-24 17:11:03 | Re: [HACKERS] Re: SSL patch |
| Previous Message | Oleg Bartunov | 1999-07-24 17:00:45 | Re: [SQL] inserts/updates problem under stressing ! |