Re: Patch for jdbc ResultSet.getTimestamp() - Mailing list pgsql-patches

From Tom Lane
Subject Re: Patch for jdbc ResultSet.getTimestamp()
Date
Msg-id 9837.990079595@sss.pgh.pa.us
Whole thread Raw
In response to Re: Patch for jdbc ResultSet.getTimestamp()  (Thomas Lockhart <lockhart@alumni.caltech.edu>)
Responses Re: Patch for jdbc ResultSet.getTimestamp()  (Bruce Momjian <pgman@candle.pha.pa.us>)
List pgsql-patches
Thomas Lockhart <lockhart@alumni.caltech.edu> writes:
>> I certainly will not be applying any jdbc stuff to 7.1.X.  I was told
>> not to apply stuff during beta.  I am sure not going to apply anything
>> to a minor release.

> OK, but if someone takes responsibility for the accuracy and
> effectiveness of a patch, then it should be considered for application.
> We had trouble during beta applying larger patches or patches which were
> not correct; some of which could be vetted by simple inspection.

Bruce got pounded (quite properly I thought) for applying patches
during late beta that he had not verified and indeed was not in a
position to verify.  The rules need to be at least as stringent for
patches that go into a stable-release branch, since we don't normally
do much beta testing for dot-releases.  But as long as someone has
adequately checked the patch, I don't think there should be a rule
against putting bug fixes into 7.1.* ...

            regards, tom lane

pgsql-patches by date:

Previous
From: Thomas Lockhart
Date:
Subject: Re: Patch for jdbc ResultSet.getTimestamp()
Next
From: Bruce Momjian
Date:
Subject: Re: Patch for jdbc ResultSet.getTimestamp()