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

Поиск
Список
Период
Сортировка
От Jacob Champion
Тема Re: [PATCH] Expose port->authn_id to extensions and triggers
Дата
Msg-id CAAWbhmhxj_g-U_BRmUcWPQ0PH3tFAkQT8YChbxSW508ApcVKXw@mail.gmail.com
обсуждение исходный текст
Ответ на Re: [PATCH] Expose port->authn_id to extensions and triggers  (Robert Haas <robertmhaas@gmail.com>)
Ответы Re: [PATCH] Expose port->authn_id to extensions and triggers  (Michael Paquier <michael@paquier.xyz>)
Список pgsql-hackers
On Thu, Jun 2, 2022 at 6:52 AM Robert Haas <robertmhaas@gmail.com> wrote:
> I'm not sure what it SHOULD be called, exactly: that's one of the hard
> problems in computer science.[1]

Yeah...

All right, here's the full list of previous suggestions, I think:

- SharedPort
- MyProcShared
- ProcParallelInfo
- ProcInfoParallel
- ParallelProcInfo
- ParallelPortInfo

I have a few new proposals:

- GlobalPortInfo
- GlobalConnInfo
- Synced[Port/Conn]Info
- Worker[Port/Conn]Info (but I think this suffers from the exact same
problem as Parallel)
- ThingsThatHappenToBeSynchronizedAcrossProcessesWhenParallelismIsInUse
- OrderImporterConsumerTemplateBeanFactory

I am struggling to come up with a single adjective that captures this
concept of sometimes-synchronized, that isn't conflicting with
existing uses (like Shared). Other suggestions are very welcome.

Thanks,
--Jacob



В списке pgsql-hackers по дате отправления:

Предыдущее
От: Mary Xu
Дата:
Сообщение: oat_post_create expected behavior
Следующее
От: Robert Haas
Дата:
Сообщение: Re: PG15 beta1 sort performance regression due to Generation context change