Re: Request for 7.0 JDBC status - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Request for 7.0 JDBC status
Date
Msg-id 4100.957283324@sss.pgh.pa.us
Whole thread Raw
In response to Re: Request for 7.0 JDBC status  (Thomas Lockhart <lockhart@alumni.caltech.edu>)
Responses Re: Request for 7.0 JDBC status  (Don Baccus <dhogaza@pacifier.com>)
Re: Request for 7.0 JDBC status  (Bruce Momjian <pgman@candle.pha.pa.us>)
List pgsql-hackers
Thomas Lockhart <lockhart@alumni.caltech.edu> writes:
>> Not to bug you Peter, but 7.0 may not wait three days before release.

> I would vote that this is important enough that it should wait, but no
> one has raised the issue until now so we haven't discussed it.

My two cents: I wouldn't object to postponing release a day or so for
it, *but* if what we're getting is an un-beta-tested driver then my
level of enthusiasm drops considerably.  I'd rather say "it'll get
fixed in 7.0.1, after a decent testing interval for the new driver".

Relevant question: how well does the JDBC code that's in CVS now
work with 7.0?  If the answer is "hardly at all" then a new driver
is probably better even if it has lurking bugs.  If the answer is
"pretty well" then again I'd be inclined to ship what we've got.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Thomas Lockhart
Date:
Subject: Hardcopy docs about ready
Next
From: Tom Lane
Date:
Subject: Re: Proposal for fixing intra-query memory leaks