Re: Fwd: Cluster "stuck" in "not accepting commands to avoid wraparound data loss"

From: Andres Freund <andres(at)anarazel(dot)de>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Fwd: Cluster "stuck" in "not accepting commands to avoid wraparound data loss"
Date: 2015-12-17 18:20:23
Message-ID: 20151217182023.GD2224@awork2.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2015-12-17 13:08:15 -0500, Robert Haas wrote:
> On Thu, Dec 17, 2015 at 12:14 PM, Andres Freund <andres(at)anarazel(dot)de> wrote:
> > On 2015-12-17 09:04:25 -0800, Jeff Janes wrote:
> >> > But I'm somewhat confused what this has to do with Andres's report.
> >>
> >> Doesn't it explain the exact situation he is in, where the oldest
> >> database is 200 million, but the cluster as a whole is 2 billion?
> >
> > There were no crashes, so no, I don't think so.
>
> Backing up a step, do we think that the fact that this was running in
> a shell rather than a screen is relevant somehow? Or did something
> happen to this particular cluster totally unrelated to that?

I reran the whole thing on a separate, but very similar, VM. Just
checked. Same thing happened. This time I have log files and
everything. No time to investigate right now, but it's reproducible if
you accept running tests for a week or so.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2015-12-17 18:20:44 Re: PATCH: postpone building buckets to the end of Hash (in HashJoin)
Previous Message Masahiko Sawada 2015-12-17 18:17:47 Re: Freeze avoidance of very large table.