Re: logical decoding / rewrite map vs. maxAllocatedDescs
Alvaro Herrera <alvherre@2ndquadrant.com>
From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: Tomas Vondra <tomas.vondra@2ndquadrant.com>
Cc: Andres Freund <andres@anarazel.de>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2018-08-13T14:46:30Z
Lists: pgsql-hackers
On 2018-Aug-11, Tomas Vondra wrote: > Hmmm, it's difficult to compare "bt full" output, but my backtraces look > somewhat different (and all the backtraces I'm seeing are 100% exactly > the same). Attached for comparison. Hmm, looks similar enough to me -- at the bottom you have the executor doing its thing, then an AcceptInvalidationMessages in the middle section atop which sit a few more catalog accesses, and further up from that you have another AcceptInvalidationMessages with more catalog accesses. AFAICS that's pretty much the same thing Andres was describing. I think the exact shape of the executor bits is not relevant, and I suppose the exact details of what occurs when invalidation messages are processed are not terribly important either. I think in Andres' backtrace there are *three* AcceptInvalidationMessages rather than two as in your case, but that shouldn't be important either, just the fact that there are N nested ones. -- Álvaro Herrera https://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
Commits
-
Close the file descriptor in ApplyLogicalMappingFile
- 43ba5ac6aa48 11.0 landed
- e00f4b68dc87 10.6 landed
- 5257b9bfbafd 9.6.11 landed
- 864ecd716a0d 9.5.15 landed
- ef1ac5b2ad08 9.4.20 landed
- fa73b377ee11 12.0 landed