| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Justin King <kingpin867(at)gmail(dot)com> |
| Cc: | pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: PG12 autovac issues |
| Date: | 2020-03-20 19:03:17 |
| Message-ID: | 20200320190317.gdxwzexdfutymqs6@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin pgsql-general |
Hi,
On 2020-03-20 12:42:31 -0500, Justin King wrote:
> When we get into this state again, is there some other information
> (other than what is in pg_stat_statement or pg_stat_activity) that
> would be useful for folks here to help understand what is going on?
If it's actually stuck on a single table, and that table is not large,
it would be useful to get a backtrace with gdb.
Greetings,
Andres Freund
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Lewis | 2020-03-20 19:17:16 | Re: PG12 autovac issues |
| Previous Message | Justin King | 2020-03-20 17:42:31 | Re: PG12 autovac issues |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2020-03-20 19:10:34 | Re: Duplicate key violation on upsert |
| Previous Message | pabloa98 | 2020-03-20 18:46:38 | Re: Could postgres12 support millions of sequences? (like 10 million) |