[Pkg-postgresql-public] Bug#766956: postgresql: 9.4 not released upstream
Karsten.Hilbert at gmx.net
Wed Oct 29 10:43:40 UTC 2014
On Mon, Oct 27, 2014 at 11:48:37AM +0100, Christoph Berg wrote:
> > If so that'd solve the apparent problem. It won't prevent
> > the following scenario though:
> > - Jessie is released with PG 9.4.betaX
> > - PG releases 9.4.betaX+1 which requires a dump/restore
> > cycle due to a catalog bump (PG doesn't "guarantuee"
> > catalog stability across betas as much as across
> > released minors)
> > - now people running PG on Debian STABLE need to
> > dump/restore their clusters
> This was the last 9.4 catversion bump.
Andrew Dunstan pushed:
- Correct volatility markings of a few json functions. json_agg and
json_object_agg and their associated transition functions should
have been marked as stable rather than immutable, as they call IO
functions indirectly. Changing this probably isn't going to make
much difference, as you can't use an aggregate function in an index
expression, but we should be correct nevertheless. json_object, on
the other hand, should be marked immutable rather than stable, as it
does not call IO functions. As discussed on -hackers, this change
is being made without bumping the catalog version, as we don't want
to do that at this stage of the cycle, and the changes are very
unlikely to affect anyone.
So it's not like it can't happen.
GPG key ID E4071346 @ eu.pool.sks-keyservers.net
E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346
More information about the Pkg-postgresql-public