| From: | "Tsunakawa, Takayuki" <tsunakawa(dot)takay(at)jp(dot)fujitsu(dot)com> |
|---|---|
| To: | 'Masahiko Sawada' <sawada(dot)mshk(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | RE: Temporary tables prevent autovacuum, leading to XID wraparound |
| Date: | 2018-02-02 06:37:46 |
| Message-ID: | 0A3221C70F24FB45833433255569204D1F8AD84F@G01JPEXMBYT05 |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
From: Masahiko Sawada [mailto:sawada(dot)mshk(at)gmail(dot)com]
> Thank you for suggestion. It sounds more smarter. So it would be more better
> if we vacuums database for anti-wraparound in ascending order of
> relfrozenxid?
I thought so, too. The current behavior is inconsistent: the launcher tries to assign all workers to one database with the biggest wraparound risk in order to eliminate the risk as fast as possible, but the workers don't get hurry to reduce the risk.
Regards
Takayuki Tsunakawa
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Khandekar | 2018-02-02 06:43:20 | Re: Query running for very long time (server hanged) with parallel append |
| Previous Message | Masahiko Sawada | 2018-02-02 06:27:06 | Re: Temporary tables prevent autovacuum, leading to XID wraparound |