Re: [HACKERS] Status report: long-query-string changes - Mailing list pgsql-hackers

From Thomas Lockhart
Subject Re: [HACKERS] Status report: long-query-string changes
Date
Msg-id 37DD1D2B.F4929265@alumni.caltech.edu
Whole thread Raw
In response to RE: [HACKERS] Status report: long-query-string changes  ("Ansley, Michael" <Michael.Ansley@intec.co.za>)
List pgsql-hackers
> Are the releases currently time based, or function based,
> or a little bit of both?

A bit of both. No new functionality would imply no new full release,
but that hasn't been a problem for the last three years ;)

imho, Tom Lane's query optimizer project and my in-progress join
syntax work would be enough to justify a new release after a couple
more months (we try to have a one month beta cycle to squash bugs and
to ensure testing across platforms). Of course, there are and will be
other new features and internal changes at least as large as the two I
mentioned which could justify the next release also.
                 - Thomas

-- 
Thomas Lockhart                lockhart@alumni.caltech.edu
South Pasadena, California


pgsql-hackers by date:

Previous
From: "Ansley, Michael"
Date:
Subject: RE: [HACKERS] Status report: long-query-string changes
Next
From: Bruce Momjian
Date:
Subject: Re: [HACKERS] pg_dump table order