On second look, it does seems the xid crossed the 2^32 mark recently, since
most tables have a frozenxid close to 4b and the current xid is ~50m:
SELECT relname, age(relfrozenxid), relfrozenxid FROM pg_class WHERE relkind =
'r' and relname not like 'pg%' order by relname;
relname |
On Fri, May 22, 2020 at 3:15 PM, Thomas Munro < thomas.mu...@gmail.com > wrote:
>
>
>
> Predicate locks are released by ClearOldPredicateLocks(), which releases
> SERIALIZABLEXACTs once they are no longer interesting. It has a
> conservative idea of what is no longer interesting: it waits until
On Fri, May 22, 2020 at 7:48 AM Mike Klaas wrote:
> It's my understanding that these locks should be cleared when there are no
> conflicting transactions. These locks had existed for > 1 week and we have
> no transactions that last more than a few seconds (the oldest transaction in
> pg_stat_a
On Thu, May 21, 2020 at 5:19 PM, Thomas Munro < thomas.mu...@gmail.com > wrote:
>
>
>
> On Fri, May 22, 2020 at 7:48 AM Mike Klaas < mike@ superhuman. com (
> m...@superhuman.com ) > wrote:
>
>
>
>>
>>
>> pid:2263461
>>
>>
>>
>
>
>
> That's an unusually high looking pid. Is that expe
On Fri, May 22, 2020 at 7:48 AM Mike Klaas wrote:
> locktype: page
> relation::regclass::text: _pkey
> virtualtransaction: 36/296299968
> granted:t
> pid:2263461
That's an unusually high looking pid. Is that expected, for example
did you crank Linux's pid_max right up, or is this AIX, or somethi
