Re: allowing broader use of simplehash

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: allowing broader use of simplehash
Date: 2019-12-17 19:17:50
Message-ID: CA+Tgmobm3VQc9jw6D+b931RpG3kNm3iug3HuUEJnD-tA00JH-Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sat, Dec 14, 2019 at 10:24 PM Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> On Thu, Dec 12, 2019 at 2:33 PM Andres Freund <andres(at)anarazel(dot)de> wrote:
> > I was basically just thinking that we could pass the context to use via
> > CurrentMemoryContext, instead of explicitly passing it in.
>
> I thought about that, but as a general rule, replacing a function
> parameter with a global variable is the wrong direction. One could
> argue this particular case is a counterexample, and I won't fight
> tooth and nail if you want to take that position, but I don't think I
> believe it myself.

After confirming with Andres that he didn't have an objection to me
pressing forward with these patches, I have committed them.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Magnus Hagander 2019-12-17 19:58:00 Re: non-exclusive backup cleanup is mildly broken
Previous Message Sergei Kornilov 2019-12-17 19:08:25 Re: global / super barriers (for checksums)