Re: BUG #16722: PG hanging on COPY when table has close to 2^32 toasts in the table.
Magnus Hagander <magnus@hagander.net>
From: Magnus Hagander <magnus@hagander.net>
To: Andres Freund <andres@anarazel.de>
Cc: Fujii Masao <masao.fujii@oss.nttdata.com>, skoposov@ed.ac.uk, PostgreSQL mailing lists <pgsql-bugs@lists.postgresql.org>
Date: 2020-11-18T22:12:10Z
Lists: pgsql-bugs
On Wed, Nov 18, 2020 at 8:27 PM Andres Freund <andres@anarazel.de> wrote: > > Hi, > > On 2020-11-18 11:57:05 +0100, Magnus Hagander wrote: > > This definitely sounds like something that's worth putting out as a > > wait event. Even before you start traversing millions of OIDs it might > > gradually start to show up, and being able to monitor that would > > definitely be useful. > > I don't think this is likely to work well as a wait event. All the index > traversals etc will do IO, acquire locks, etc, which will overwrite the > wait event and reset it to nothing once done. Oh meh. Yeah, I didn't think about the actual implementation of doing it :/ That said, I'd really prefer to see *some* kind of counter that could get people noticing this a bit earlier, rather than just bugging them in the logfile once it's gone over a threshold. A statistics counter maybe, but I guess that'd have to be tracked at a per-table level to be really useful, which would make it potentially fairly expensive to keep around... -- Magnus Hagander Me: https://www.hagander.net/ Work: https://www.redpill-linpro.com/
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Log when GetNewOidWithIndex() fails to find unused OID many times.
- 7fbcee1b2d5f 14.0 landed
-
Add tests for bytea LIKE operator
- eb42110d952f 14.0 cited