From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Jakub Jedelský <jakub(dot)jedelsky(at)gmail(dot)com> |
Cc: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: Autovacuum of pg_database |
Date: | 2017-05-15 17:29:28 |
Message-ID: | 15834.1494869368@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
=?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
From | Date | Subject | |
---|---|---|---|
Next Message | Jakub Jedelsky | 2017-05-15 19:26:54 | Re: Autovacuum of pg_database |
Previous Message | Jakub Jedelský | 2017-05-15 08:55:51 | Autovacuum of pg_database |