From: Tom Lane <tgl@sss.pgh.pa.us>
To: =?UTF-8?Q?Jakub_Jedelsk=C3=BD?= <jakub.jedelsky@gmail.com>
cc: pgsql-admin@postgresql.org
Subject: Re: Autovacuum of pg_database
In-reply-to: 
 <CAE9--j-08gTnFHab0t-fcuEUvsW=pw3yuPD46FCdzwV7rNfcGw@mail.gmail.com>
References: 
 <CAE9--j-08gTnFHab0t-fcuEUvsW=pw3yuPD46FCdzwV7rNfcGw@mail.gmail.com>
Comments: In-reply-to =?UTF-8?Q?Jakub_Jedelsk=C3=BD?=
 <jakub.jedelsky@gmail.com>
	message dated "Mon, 15 May 2017 10:55:51 +0200"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <15833.1494869368.1@sss.pgh.pa.us>
Date: Mon, 15 May 2017 13:29:28 -0400
Message-ID: <15834.1494869368@sss.pgh.pa.us>
Precedence: bulk
Sender: pgsql-admin-owner@postgresql.org

=?UTF-8?Q?Jakub_Jedelsk=C3=BD?= <jakub.jedelsky@gmail.com> writes:
> The problem (can) occurs when the pg_database table hits
> `autovacuum_freeze_max_age` and I'm able to reporoduce it (but not always)
> with this stupid reproducer:
> * set autovacuum_freeze_min_age to it's minimum - 100000
> * generating ~ 1000 DBs
> * make some transactions to almost hit `autovacuum_freeze_max_age`
> * `vacuum freeze` all tables in all databases except pg_database
> * run a few transactions to hit `autovacuum_freeze_max_age`

I tried to reverse-engineer a test case out of this description,
without much success.  If you have a script that can reproduce
the problem (even if not 100% success rate), could you share it?

			regards, tom lane


-- 
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin