Re: PgUpgrade bumped my XIDs by ~50M?

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Jerry Sievers <gsievers19(at)comcast(dot)net>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: PgUpgrade bumped my XIDs by ~50M?
Date: 2018-04-05 00:29:06
Message-ID: 20180405002906.GE19574@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Wed, Apr 4, 2018 at 07:13:36PM -0500, Jerry Sievers wrote:
> Bruce Momjian <bruce(at)momjian(dot)us> writes:
> > Is it possible that pg_upgrade used 50M xids while upgrading?
>
> Hi Bruce.
>
> Don't think so, as I did just snap the safety snap and ran another
> upgrade on that.
>
> And I also compared txid_current for the upgraded snap and our running
> production instance.
>
> The freshly upgraded snap is ~50M txids behind the prod instance.

Are the objects 50M behind or is txid_current 50M different? Higher or
lower?

>
> If this is a not too uncommon case of users running amok, then this time
> in particular they really went off the charts :-)

I have never heard of this problem.

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ As you are, so once was I. As I am, so you will be. +
+ Ancient Roman grave inscription +

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Peter Eisentraut 2018-04-05 00:40:58 Re: LDAP Bind Password
Previous Message Paul Jungwirth 2018-04-05 00:17:05 Extension make installcheck: include update/insert feedback?