Re: Refactoring SysCacheGetAttr to know when attr cannot be NULL

From: Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>
To: David Rowley <dgrowleyml(at)gmail(dot)com>, Daniel Gustafsson <daniel(at)yesql(dot)se>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Refactoring SysCacheGetAttr to know when attr cannot be NULL
Date: 2023-03-24 07:31:04
Message-ID: 77811974-e9a7-da08-dc60-ca9f1f787c42@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 23.03.23 09:52, David Rowley wrote:
> One thing I thought about while looking is it stage 2 might do
> something similar for SearchSysCacheN. I then wondered if we're more
> likely to want to keep the localised __FILE__, __LINE__ and __func__
> in the elog for those or not. It's probably less important that we're
> losing those for this change, but worth noting here at least in case
> nobody else thought of it.

I don't follow what you are asking for here.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2023-03-24 07:50:57 Re: ICU locale validation / canonicalization
Previous Message Andres Freund 2023-03-24 07:26:19 Re: meson documentation build open issues