Hello.
Got some new information.
There are 6 replicas and master in cluster. I rebooted two replicas... And
they started to work as expected!
So, on master and 4 untouched replicas:
txid_current() -> 4459388265
txid_status(BIGINT '4459388265') -> NULL
On two rebooted replicas:
txid_status(BIGIN
Hi, thanks for the reply!
> What are you using it for?
I want to use it to validate status of related entities in other database
(queue) in short interval after PG transaction commit/rollback.
> I can't reproduce that...
Yes, it happens only with one cluster. All others work as expected.
> You
Hi,
On 2018-09-25 19:47:40 +0300, Michail Nikolaev wrote:
> I see strange beaviour of txid_status with one of my production servers.
What are you using it for?
> SELECT txid_status(txid_current()) -> NULL
I can't reproduce that...
> SELECT txid_current() -> 4447342811
>
> It also returns nu
Sorry, some auto formatting in recent email.
Again wtih fixed formatiing:
I see strange beaviour of txid_status with one of my production servers.
SELECT txid_status(txid_current()) -> NULL
SELECT txid_current() -> 4447342811
It also returns null for recent commited and aborted transactions.
S
Hello everyone.
I see strange beaviour of txid_status with one of my production servers.
SELECT txid_status(txid_current()) -> NULL
SELECT txid_current() -> 4447342811
It also returns null for recent commited and aborted transactions.
SELECT datname, age(datfrozenxid), datfrozenxid FROM pg_data
