Re: questions about wraparound

From: Luca Ferrari <fluca1978(at)gmail(dot)com>
To: pgsql-general <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: questions about wraparound
Date: 2021-03-29 08:33:15
Message-ID: CAKoxK+4YJm4cF6ZRCe6D36GiwqQP8B-WtOL_+tjU3RfNgBrLEA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Mon, Mar 22, 2021 at 8:56 AM Luca Ferrari <fluca1978(at)gmail(dot)com> wrote:
> backend> select datname, age( datfrozenxid), current_setting(
> 1: datname = "template0" (typeid = 19, len = 64, typmod
> = -1, byval = f)
> 2: age = "2138438218" (typeid = 23, len = 4, typmod = -1, byval = t)
> 3: current_setting = "50000000" (typeid = 25, len =
> -1, typmod = -1, byval = f)
> ----
> 1: datname = "testdb" (typeid = 19, len = 64, typmod = -1, byval = f)
> 2: age = "2138438218" (typeid = 23, len = 4, typmod = -1, byval = t)
> 3: current_setting = "50000000" (typeid = 25, len =
> -1, typmod = -1, byval = f)

Another thing that comes into my mind as a doubt is: why are all
databases becoming old? I mean, I'm provoking activity _only_ on
testdb, therefore other database such as template1 are not doing
anything. Why an emergency autovacuum is not freezing such databases
before the wraparound happens?

Luca

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Laurenz Albe 2021-03-29 09:14:21 Re: questions about wraparound
Previous Message NEERAJ BANSAL 2021-03-29 06:00:29 search_path in pg_dump output.