From: | Peter Geoghegan <pg(at)bowt(dot)ie> |
---|---|
To: | Masahiko Sawada <masahiko(dot)sawada(at)2ndquadrant(dot)com> |
Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: xid wraparound danger due to INDEX_CLEANUP false |
Date: | 2020-05-23 00:25:04 |
Message-ID: | CAH2-WzkTzKUvWvP76aoL0ZQLC3fvxjpuy8TqA=1RAZm8cC=e8Q@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, May 22, 2020 at 1:40 PM Peter Geoghegan <pg(at)bowt(dot)ie> wrote:
> It. seems like the right direction to me. Robert?
BTW, this is an interesting report of somebody using the INDEX_CLEANUP
feature when they had to deal with a difficult production issue:
https://www.buildkitestatus.com/incidents/h0vnx4gp7djx
This report is not really relevant to our discussion, but I thought
you might find it interesting.
--
Peter Geoghegan
From | Date | Subject | |
---|---|---|---|
Next Message | Amit Kapila | 2020-05-23 04:34:54 | Re: Parallel Seq Scan vs kernel read ahead |
Previous Message | Alvaro Herrera | 2020-05-22 23:32:57 | Re: segmentation fault using currtid and partitioned tables |