Back-branch update releases scheduled

Started by Tom Laneabout 11 years ago5 messageshackers
Jump to latest
#1Tom Lane
tgl@sss.pgh.pa.us

We're really rather overdue for updates of the pre-9.4 back branches,
and 9.4 itself has probably baked for long enough to justify a 9.4.1.
Accordingly, the core committee has agreed to wrap releases the week
after next; that's wrap Mon Feb 2 for public announcement Thu Feb 5.

regards, tom lane

--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

In reply to: Tom Lane (#1)
Re: Back-branch update releases scheduled

On Thu, Jan 22, 2015 at 3:23 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:

We're really rather overdue for updates of the pre-9.4 back branches,
and 9.4 itself has probably baked for long enough to justify a 9.4.1.
Accordingly, the core committee has agreed to wrap releases the week
after next; that's wrap Mon Feb 2 for public announcement Thu Feb 5.

I hope that gives us enough time to fix the issue in question in the
9.4.0 problem report thread "hung backends stuck in spinlock heavy
endless loop".

--
Peter Geoghegan

--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

#3Bruce Momjian
bruce@momjian.us
In reply to: Peter Geoghegan (#2)
Re: Back-branch update releases scheduled

On Thu, Jan 22, 2015 at 03:28:39PM -0800, Peter Geoghegan wrote:

On Thu, Jan 22, 2015 at 3:23 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:

We're really rather overdue for updates of the pre-9.4 back branches,
and 9.4 itself has probably baked for long enough to justify a 9.4.1.
Accordingly, the core committee has agreed to wrap releases the week
after next; that's wrap Mon Feb 2 for public announcement Thu Feb 5.

I hope that gives us enough time to fix the issue in question in the
9.4.0 problem report thread "hung backends stuck in spinlock heavy
endless loop".

The JSON/JSONB escape thing would be nice to fix too, before the
existing behavior becomes too baked into applications.

--
Bruce Momjian <bruce@momjian.us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ Everyone has their own god. +

--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

#4Tom Lane
tgl@sss.pgh.pa.us
In reply to: Bruce Momjian (#3)
Re: Back-branch update releases scheduled

Bruce Momjian <bruce@momjian.us> writes:

On Thu, Jan 22, 2015 at 03:28:39PM -0800, Peter Geoghegan wrote:

On Thu, Jan 22, 2015 at 3:23 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:

We're really rather overdue for updates of the pre-9.4 back branches,
and 9.4 itself has probably baked for long enough to justify a 9.4.1.
Accordingly, the core committee has agreed to wrap releases the week
after next; that's wrap Mon Feb 2 for public announcement Thu Feb 5.

I hope that gives us enough time to fix the issue in question in the
9.4.0 problem report thread "hung backends stuck in spinlock heavy
endless loop".

The JSON/JSONB escape thing would be nice to fix too, before the
existing behavior becomes too baked into applications.

So let's get on with it. We're not holding up releases for patches
that may or may not materialize.

regards, tom lane

--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

In reply to: Tom Lane (#4)
Re: Back-branch update releases scheduled

On Thu, Jan 22, 2015 at 3:51 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:

So let's get on with it. We're not holding up releases for patches
that may or may not materialize.

I don't disagree. Just pointing out that it's a consideration.

--
Peter Geoghegan

--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers