[HACKERS] oldest xmin is far in the past

Hi everyone! Trying to make VACUUM FREEZE on PG instance and keep getting this error: 2016-03-18 05:56:51 UTC 46750 WARNING: oldest xmin is far in the past 2016-03-18 05:56:51 UTC 46750 HINT: Close open transactions soon to avoid wraparound problems. 2016-03-18 05:56:51 UTC 46750 DEBUG:

Re: [HACKERS] oldest xmin is far in the past

is weird. How can I calculate how long DB can live in this stage? 2016-03-19 0:28 GMT+03:00 Tomas Vondra : > Hi, > > On 03/18/2016 09:42 AM, John Snow wrote: > >> Hi everyone! >> >> Trying to make VACUUM FREEZE on PG instance and keep getting this error: >>