Hi, On 2018-05-22 22:18:15 +0300, Maxim Boguk wrote: > On Tue, May 22, 2018 at 9:47 PM, Andres Freund <andres@xxxxxxxxxxx> wrote: > > > select relfrozenxid from pg_class where relname='pg_authid'; > > > relfrozenxid > > > -------------- > > > 2863429136 > select txid_current(); > txid_current > -------------- > 41995913769 So that's an xid of 3341208114, if you leave the epoch out. What's autovacuum_freeze_max_age set to in that cluster? Can you show pg_controldata output, and relminmxid from that cluster? I might be daft here, but it's surely curious that the relfrozenxid from the error and pg_catalog are really different (number of digits): catalog: 2863429136 error: 248712603 > About gdb bt - it's tricky because it is mission critical master db of > huge project. > I'll will try promote backup replica and check is issue persist there and > if yes - we will have our playground for a while, but it will require > sometime to arrange. You should be ok to just bt that in the running cluster, but I definitely understand if you don't want to do that... I'd appreciate if you set up the a playground, because this seems like something that'll reappear. Greetings, Andres Freund
