Date: Mon, 15 May 2017 21:26:54 +0200
From: Jakub Jedelsky <jakub.jedelsky@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-admin@postgresql.org
Subject: Re: Autovacuum of pg_database
Message-ID: <20170515192653.GA23721@gd-kuba.localdomain>
References: 
 <CAE9--j-08gTnFHab0t-fcuEUvsW=pw3yuPD46FCdzwV7rNfcGw@mail.gmail.com>
 <15834.1494869368@sss.pgh.pa.us>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <15834.1494869368@sss.pgh.pa.us>
User-Agent: Mutt/1.8.0 (2017-02-23)
Precedence: bulk
Sender: pgsql-admin-owner@postgresql.org

On Mon, May 15, 2017 at 01:29:28PM -0400, Tom Lane wrote:
> =?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

Thanks for reply. I will try to prepare something asap, but it can
take some time, so please be patient. (I just want to make you sure,
that I'm not ignoring that thread :))

Regards, jj.


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