Bruce Momjian writes:
> On Wed, Apr 4, 2018 at 08:29:06PM -0400, Bruce Momjian wrote:
>
>> On Wed, Apr 4, 2018 at 07:13:36PM -0500, Jerry Sievers wrote:
>> > Bruce Momjian writes:
>> > > Is it possible that pg_upgrade used 50M xids while upgrading?
>> >
>>
Jerry Sievers writes:
> Bruce Momjian writes:
>
>> On Wed, Apr 4, 2018 at 07:13:36PM -0500, Jerry Sievers wrote:
>>
>>> Bruce Momjian writes:
>>> > Is it possible that pg_upgrade used 50M xids while upgrading?
>>>
>>> Hi Bruce.
>>>
On Wed, Apr 4, 2018 at 07:13:36PM -0500, Jerry Sievers wrote:
> Bruce Momjian 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
Bruce Momjian writes:
> On Wed, Apr 4, 2018 at 05:29:46PM -0500, Jerry Sievers wrote:
>
>> We have a large >20TB system just pg_upgraded from 9.5 to 9.6 as per the
>> versions shown below.
>>
>> The system does <5M transactions/day based on sum(commit + abort) from
>>
On Wed, Apr 4, 2018 at 05:29:46PM -0500, Jerry Sievers wrote:
> We have a large >20TB system just pg_upgraded from 9.5 to 9.6 as per the
> versions shown below.
>
> The system does <5M transactions/day based on sum(commit + abort) from
> pg_stat_database.
>
> Autovac is running all possible
We have a large >20TB system just pg_upgraded from 9.5 to 9.6 as per the
versions shown below.
The system does <5M transactions/day based on sum(commit + abort) from
pg_stat_database.
Autovac is running all possible threads now and upon investigating I see
that thousands of tables are now above