From: | Jakub Jedelsky <jakub(dot)jedelsky(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: Autovacuum of pg_database |
Date: | 2017-05-15 19:26:54 |
Message-ID: | 20170515192653.GA23721@gd-kuba.localdomain |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
On Mon, May 15, 2017 at 01:29:28PM -0400, Tom Lane wrote:
> =?UTF-8?Q?Jakub_Jedelsk=C3=BD?= <jakub(dot)jedelsky(at)gmail(dot)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.
From | Date | Subject | |
---|---|---|---|
Next Message | rakesh-eltropy | 2017-05-16 07:43:02 | Postgres Data Encryption Using LUKS with dm-crypt |
Previous Message | Tom Lane | 2017-05-15 17:29:28 | Re: Autovacuum of pg_database |