Re: Boundary value check in lazy_tid_reaped()

From: Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>
To: Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>
Cc: Masahiko Sawada <masahiko(dot)sawada(at)2ndquadrant(dot)com>, Peter Geoghegan <pg(at)bowt(dot)ie>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Boundary value check in lazy_tid_reaped()
Date: 2021-03-10 14:53:29
Message-ID: e68ce7f9-85d1-1f58-c3ba-4b77543629c3@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 10.03.21 02:29, Masahiko Sawada wrote:
>> There is no noticeable effect of inlining lazy_tid_reaped(). So it
>> would be better to not do that.
>
> Attached the patch that doesn't inline lazy_tid_reaped().

committed

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Langote 2021-03-10 15:44:53 Re: Huge memory consumption on partitioned table with FKs
Previous Message David Steele 2021-03-10 14:38:39 Re: WIP: document the hook system