On Tue, Jun 9, 2015 at 3:04 AM, David Gould wrote:
> On Mon, 8 Jun 2015 13:53:42 -0300
> Alvaro Herrera wrote:
>
>> * people with the wrong oldestMulti setting in pg_control (which would
>> be due to a buggy pg_upgrade being used long ago) will be unable to
>> start if they upgrade to 9.3.7 or 9.
On Mon, 8 Jun 2015 13:53:42 -0300
Alvaro Herrera wrote:
> * people with the wrong oldestMulti setting in pg_control (which would
> be due to a buggy pg_upgrade being used long ago) will be unable to
> start if they upgrade to 9.3.7 or 9.3.8. A solution for them would be
> to downgrade to 9.3.6.
Josh Berkus wrote:
> On 06/08/2015 12:48 PM, Alvaro Herrera wrote:
> > Well, reputation-wise we're already losing every time somebody's server
> > crashes on 9.4.2 and finds it won't start, where it did start fine with
> > 9.4.1. Maybe they simply wanted to change shared_buffers and the server
> >
On 06/08/2015 12:48 PM, Alvaro Herrera wrote:
> Well, reputation-wise we're already losing every time somebody's server
> crashes on 9.4.2 and finds it won't start, where it did start fine with
> 9.4.1. Maybe they simply wanted to change shared_buffers and the server
> won't start anymore. Some p
On 06/08/2015 12:48 PM, Alvaro Herrera wrote:
Well, reputation-wise we're already losing every time somebody's server
crashes on 9.4.2 and finds it won't start, where it did start fine with
9.4.1. Maybe they simply wanted to change shared_buffers and the server
won't start anymore. Some peopl
Joshua D. Drake wrote:
>
> On 06/08/2015 12:31 PM, Alvaro Herrera wrote:
> >
> >Joshua D. Drake wrote:
> >
> >>If we release on Friday that is the 12th, PgCon is starts the 16th and there
> >>is a weekend in between. If there is an unknown regression or new bug that
> >>is severe, are we going to
On 06/08/2015 12:31 PM, Alvaro Herrera wrote:
Joshua D. Drake wrote:
If we release on Friday that is the 12th, PgCon is starts the 16th and there
is a weekend in between. If there is an unknown regression or new bug that
is severe, are we going to have the resources to resolve it?
ISTM if t
Joshua D. Drake wrote:
> If we release on Friday that is the 12th, PgCon is starts the 16th and there
> is a weekend in between. If there is an unknown regression or new bug that
> is severe, are we going to have the resources to resolve it?
ISTM if that happens, we're no worse off than currently
On 06/08/2015 12:21 PM, Tom Lane wrote:
Andres Freund writes:
On 2015-06-08 14:18:22 -0400, Tom Lane wrote:
As I saw it, on Friday it was not clear whether we would be able to do a
release this week. Now it's Monday, and we still have a rather long list
of issues
Well, these issues aren't
Andres Freund writes:
> On 2015-06-08 14:18:22 -0400, Tom Lane wrote:
>> As I saw it, on Friday it was not clear whether we would be able to do a
>> release this week. Now it's Monday, and we still have a rather long list
>> of issues
> Well, these issues aren't regressions, they're "just" gener
On Mon, Jun 8, 2015 at 2:18 PM, Tom Lane wrote:
> As I saw it, on Friday it was not clear whether we would be able to do a
> release this week. Now it's Monday, and we still have a rather long list
> of issues, and apparently Andres isn't all that happy even with the fixes
> that have gone in, be
On 2015-06-08 14:18:22 -0400, Tom Lane wrote:
> As I saw it, on Friday it was not clear whether we would be able to do a
> release this week. Now it's Monday, and we still have a rather long list
> of issues
Well, these issues aren't regressions, they're "just" general problems
we need to fix. An
Robert Haas writes:
> It's not exactly going into a black hole, but there was some
> communication between Tom and Andres on Friday that left Andres with
> the impression that if he spent the weekend testing the new code for
> problems and things went well, we'd be able to get a release this
> wee
On 2015-06-08 13:16:00 -0400, Robert Haas wrote:
> It's not exactly going into a black hole, but there was some
> communication between Tom and Andres on Friday that left Andres with
> the impression that if he spent the weekend testing the new code for
> problems and things went well, we'd be able
Bruce Momjian wrote:
> On Mon, Jun 8, 2015 at 02:01:52PM -0300, Alvaro Herrera wrote:
> > > OK, are these fixed in 9.4.2 or would the same failure happen in 9.4.3?
> >
> > The fixes are not yet in any released branch, hence the rush to get
> > these out.
>
> OK, now I understand. :-O We have
On Mon, Jun 8, 2015 at 1:08 PM, Bruce Momjian wrote:
> OK, now I understand. :-O We have known failures that are not patched,
> hence the desire for a release.
>
> I am a little concerned we are getting into a case where community
> members dedicated to this issue are asking for a release, and i
On Mon, Jun 8, 2015 at 02:01:52PM -0300, Alvaro Herrera wrote:
> Bruce Momjian wrote:
> > On Mon, Jun 8, 2015 at 12:39:24PM -0400, Robert Haas wrote:
> > > On Mon, Jun 8, 2015 at 12:36 PM, Bruce Momjian wrote:
> > > > Yeah, I think if we needed this out in an emergency, we would do it, but
> > >
Bruce Momjian wrote:
> On Mon, Jun 8, 2015 at 12:39:24PM -0400, Robert Haas wrote:
> > On Mon, Jun 8, 2015 at 12:36 PM, Bruce Momjian wrote:
> > > Yeah, I think if we needed this out in an emergency, we would do it, but
> > > based on the volume of recent releases, it would be hard. Are we seein
On Mon, Jun 8, 2015 at 01:53:42PM -0300, Alvaro Herrera wrote:
> * people with the wrong oldestMulti setting in pg_control (which would
> be due to a buggy pg_upgrade being used long ago) will be unable to
> start if they upgrade to 9.3.7 or 9.3.8. A solution for them would be
> to downgrade to 9
On Mon, Jun 8, 2015 at 12:39:24PM -0400, Robert Haas wrote:
> On Mon, Jun 8, 2015 at 12:36 PM, Bruce Momjian wrote:
> > Yeah, I think if we needed this out in an emergency, we would do it, but
> > based on the volume of recent releases, it would be hard. Are we seeing
> > user reports of failure
Bruce Momjian wrote:
> On Mon, Jun 8, 2015 at 11:40:43AM -0400, Tom Lane wrote:
> > Robert Haas writes:
> > > So, when shall we do all of this releasing? It seems like we could do
> > > stage-one of the multixact fixing this week, and then figure out how
> > > to do the other stuff after PGCon.
On Mon, Jun 8, 2015 at 12:36 PM, Bruce Momjian wrote:
> Yeah, I think if we needed this out in an emergency, we would do it, but
> based on the volume of recent releases, it would be hard. Are we seeing
> user reports of failures even on the newest released versions, or are
> these preventive fix
On Mon, Jun 8, 2015 at 11:40:43AM -0400, Tom Lane wrote:
> Robert Haas writes:
> > So, when shall we do all of this releasing? It seems like we could do
> > stage-one of the multixact fixing this week, and then figure out how
> > to do the other stuff after PGCon. Alternatively, we can let the
Robert Haas writes:
> So, when shall we do all of this releasing? It seems like we could do
> stage-one of the multixact fixing this week, and then figure out how
> to do the other stuff after PGCon. Alternatively, we can let the
> latest round of changes that are already in the tree settle unti
Hi,
I think we have consensus that we should proceed with releasing fixes
for the known multixact bugs in two stages:
- One set of minor releases with the fixes that we have now, to undo
the damage caused by 9.4.2 and still present in 9.4.3. These changes
will force immediate anti-wraparound vac
25 matches
Mail list logo