> On 8 May 2023, at 10:39, Daniel Gustafsson wrote:
>> On 4 May 2023, at 14:18, Daniel Gustafsson wrote:
>>> On 4 May 2023, at 14:09, Tom Lane wrote:
>>> How about naming
>>> the hash "EventTriggerCacheHash" or so?
>>
>> I think the level is the indicator here, but I have no strong opinions,
>
On Mon, May 08, 2023 at 10:39:42AM +0200, Daniel Gustafsson wrote:
> On 4 May 2023, at 14:18, Daniel Gustafsson wrote:
>> On 4 May 2023, at 14:09, Tom Lane wrote:
>>> Hmm, I'm kinda -1 on them having the same name visible in the
>>> contexts dump --- that seems very confusing. How about naming
>
> On 4 May 2023, at 14:18, Daniel Gustafsson wrote:
>
>> On 4 May 2023, at 14:09, Tom Lane wrote:
>>
>> Daniel Gustafsson writes:
>>> When reading a memory contexts log I realized that we have this:
>>> LOG: level: 2; EventTriggerCache: 8192 total in 1 blocks; 7928 free (4
>>> chunks); 264 u
> On 4 May 2023, at 14:09, Tom Lane wrote:
>
> Daniel Gustafsson writes:
>> When reading a memory contexts log I realized that we have this:
>> LOG: level: 2; EventTriggerCache: 8192 total in 1 blocks; 7928 free (4
>> chunks); 264 used
>> LOG: level: 3; Event Trigger Cache: 8192 total in 1 bl
Daniel Gustafsson writes:
> When reading a memory contexts log I realized that we have this:
> LOG: level: 2; EventTriggerCache: 8192 total in 1 blocks; 7928 free (4
> chunks); 264 used
> LOG: level: 3; Event Trigger Cache: 8192 total in 1 blocks; 2616 free (0
> chunks); 5576 used
> The reaso
When reading a memory contexts log I realized that we have this:
LOG: level: 2; EventTriggerCache: 8192 total in 1 blocks; 7928 free (4
chunks); 264 used
LOG: level: 3; Event Trigger Cache: 8192 total in 1 blocks; 2616 free (0
chunks); 5576 used
The reason is that BuildEventTriggerCache sets
