Re: [PATCH] Expose port->authn_id to extensions and triggers

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Jacob Champion <jchampion(at)timescale(dot)com>
Cc: Michael Paquier <michael(at)paquier(dot)xyz>, "sfrost(at)snowman(dot)net" <sfrost(at)snowman(dot)net>, "rjuju123(at)gmail(dot)com" <rjuju123(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, "tgl(at)sss(dot)pgh(dot)pa(dot)us" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "andres(at)anarazel(dot)de" <andres(at)anarazel(dot)de>
Subject: Re: [PATCH] Expose port->authn_id to extensions and triggers
Date: 2022-06-02 13:51:51
Message-ID: CA+TgmobAjhB5xpQ+9pP4mmaWgB53=nwXYELscVEXBByRRS40VA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, May 31, 2022 at 6:21 PM Jacob Champion <jchampion(at)timescale(dot)com> wrote:
> v10 is rebased over latest; I've also added a PGDLLIMPORT to the new global.

I took a quick look at this and it doesn't seem crazy to me, except
that I think ParallelProcInfo is a bad name for it. It's kind of
generic, because neither "proc" nor "info" means a whole lot. It's
also kind of wrong, because I think "parallel" should be things that
have to do with parallelism, not just things that happen to be
synchronized across processes when parallelism is in use. It doesn't
make sense to me to have something called a ParallelProcInfo that is
used for every single connection in the universe even if parallelism
is completely disabled on the system.

I'm not sure what it SHOULD be called, exactly: that's one of the hard
problems in computer science.[1]

--
Robert Haas
EDB: http://www.enterprisedb.com

[1] https://martinfowler.com/bliki/TwoHardThings.html

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Matthias van de Meent 2022-06-02 14:27:25 Re: compiler warnings with gcc 4.8 and -Og
Previous Message Daniel Gustafsson 2022-06-02 13:32:10 Re: compiler warnings with gcc 4.8 and -Og