Re: maximum number of backtrace frames logged by backtrace_functions

On 2022/02/04 9:48, Fujii Masao wrote: On 2022/02/03 23:48, Tom Lane wrote: Peter Eisentraut writes: How about we issue a message when the backtrace is cut off.  Then it's immediately visible to the user, instead of hidden away somewhere in the documentation.  Something like this

Re: documentation on HOT

On 2/6/22 8:56 PM, David G. Johnston wrote: On Sun, Feb 6, 2022 at 6:08 PM Jonathan S. Katz > wrote: Given the importance of HOT, it seems like this would be a good topic to document. I would suggest something higher-level for general users in the

Re: documentation on HOT

On Sun, Feb 6, 2022 at 6:08 PM Jonathan S. Katz wrote: > > Given the importance of HOT, it seems like this would be a good topic to > document. I would suggest something higher-level for general users in > the "Indexes"[4] section, and something lower-level in internals[5] > (which could perhaps

documentation on HOT

Hi, While working on the 2020-02-10 release announcement, in order to better describe one of the fixes, I tried to find a reference in the docs that described what HOT is, how it works, etc. in a user-friendly manner. This lead me to the acronyms page[1], which lead me to a document in the