Re: not null constraints, again

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
Cc: Tender Wang <tndrwang(at)gmail(dot)com>, jian he <jian(dot)universality(at)gmail(dot)com>, Pg Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: not null constraints, again
Date: 2025-04-15 21:12:42
Message-ID: 1734523.1744751562@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> writes:
> On 2025-Apr-15, Tom Lane wrote:
>> Looking at the patch itself, it doesn't seem like the got_children
>> flag is accomplishing anything;

> Ah yes, I forgot to set got_children when reading the children list.
> This happens within the loop for columns, so the idea is to obtain that
> list just once instead of once per column.

Ah, got it. Makes sense as long as you actually avoid the work ;-)

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Daniel Gustafsson 2025-04-15 21:18:16 Re: Align memory context level numbering in pg_log_backend_memory_contexts()
Previous Message Alvaro Herrera 2025-04-15 21:10:26 Re: not null constraints, again