Re: [PATCH] Expose port->authn_id to extensions and triggers
От | Robert Haas |
---|---|
Тема | Re: [PATCH] Expose port->authn_id to extensions and triggers |
Дата | |
Msg-id | CA+TgmobAjhB5xpQ+9pP4mmaWgB53=nwXYELscVEXBByRRS40VA@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: [PATCH] Expose port->authn_id to extensions and triggers (Jacob Champion <jchampion@timescale.com>) |
Ответы |
Re: [PATCH] Expose port->authn_id to extensions and triggers
|
Список | pgsql-hackers |
On Tue, May 31, 2022 at 6:21 PM Jacob Champion <jchampion@timescale.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
В списке pgsql-hackers по дате отправления: