| From: | Tomas Vondra <tomas(at)vondra(dot)me> |
|---|---|
| To: | Peter Geoghegan <pg(at)bowt(dot)ie> |
| Cc: | Mark Dilger <mark(dot)dilger(at)enterprisedb(dot)com>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, pgsql-hackers(at)lists(dot)postgresql(dot)org, Matthias van de Meent <boekewurm+postgres(at)gmail(dot)com> |
| Subject: | Re: Adding skip scan (including MDAM style range skip scan) to nbtree |
| Date: | 2025-05-09 14:51:10 |
| Message-ID: | 0e5da454-c337-4569-bb23-302560d793b9@vondra.me |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 5/9/25 16:17, Peter Geoghegan wrote:
> On Fri, May 9, 2025 at 8:58 AM Tomas Vondra <tomas(at)vondra(dot)me> wrote:
>> I'm also not sure about the root cause, but while investigating it one
>> of the experiments I tried was tweaking the glibc malloc by setting
>>
>> export MALLOC_TOP_PAD_=$((64*1024*1024))
>>
>> which keeps a 64MB "buffer" in glibc, to reduce the amount of malloc
>> syscalls. And with that, the results change to this:
>
> You're sure that the problem is an increase in the number of
> malloc()s? If that's what this is, then it shouldn't be too hard to
> debug.
>
No, I'm not sure. I merely speculate based on the observation that
setting the environment variable makes the issue go away.
I've seen similar problems with btree before, as it allocates fairly
large chunks of memory for BTScanOpaque.
--
Tomas Vondra
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Shlok Kyal | 2025-05-09 14:55:17 | Re: Restrict publishing of partitioned table with a foreign table as partition |
| Previous Message | Ashutosh Bapat | 2025-05-09 14:43:02 | Re: Changing shared_buffers without restart |