Skip site navigation (1) Skip section navigation (2)

Fw: PATCH (Re: Startup message issues)

From: "Chris Smith" <cdsmith(at)twu(dot)net>
To: <pgsql-jdbc(at)postgresql(dot)org>
Subject: Fw: PATCH (Re: Startup message issues)
Date: 2004-02-13 18:56:42
Message-ID: 010a01c3f263$1ee9d1b0$6f00000a@KYA (view raw, whole thread or download thread mbox)
Lists: pgsql-jdbc
Sorry.  Again forgot to copy the list.  (I'll get the hang of this
eventually...).  Here's what I mistakenly sent only to Kris, but meant to send
to the list.

Chris Smith wrote:
> Kris Jurka wrote:
> > This would be a good thing to do.  I believe the V3 protocol was put
> > in with the goal of getting it working which meant a copy, paste,
> > and minimal edit.  So yes V3 implies 7.4 and it would be nice if it
> > took full advantage of what is offered.
> Okay, great!  Could someone review the attached patch?  It makes the
> following changes:
>     1. Remove backward-compatibility for pre-7.4 versions from
>        the v3 protocol connection code.
>     2. Move client_encoding and DateStyle setup to startup message.
>     3. Parse ParameterStatus for server_version.
> The result of #2 and #3 is that v3 protocol connections are
> established with only one round-trip to the server (in the trust auth
> case; two when authentication is required).  I've done some ad-hoc
> testing... is there a test suite that should be run against this?

The Easiest Way to Train Anyone... Anywhere.

Chris Smith - Lead Software Developer/Technical Trainer
MindIQ Corporation

Attachment: jdbc-v3-openconn.patch
Description: application/octet-stream (8.4 KB)


pgsql-jdbc by date

Next:From: Dave CramerDate: 2004-02-13 18:59:10
Subject: Re: Startup message issues
Previous:From: John Sidney-WoollettDate: 2004-02-13 18:56:29
Subject: Re: Serial key

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group