Re: Random PGDLLIMPORTing

Поиск
Список
Период
Сортировка
Искать
От
Michael Paquier
Тема
Re: Random PGDLLIMPORTing
Дата
Msg-id
CAB7nPqRGHoXraX-uh=mexo4qNRN0teK0FZnV0LNRaAtmiLuzgg@mail.gmail.com
Ответ на
Re: Random PGDLLIMPORTing (Magnus Hagander)
Список
Дерево обсуждения
Random PGDLLIMPORTing Craig Ringer <craig@2ndquadrant.com>
Re: Random PGDLLIMPORTing Magnus Hagander <magnus@hagander.net>
Re: Random PGDLLIMPORTing Victor Wagner <vitus@wagner.pp.ru>
Re: Random PGDLLIMPORTing Michael Paquier <michael.paquier@gmail.com>
Re: Random PGDLLIMPORTing Craig Ringer <craig@2ndquadrant.com>
Re: Random PGDLLIMPORTing Tom Lane <tgl@sss.pgh.pa.us>
Re: Random PGDLLIMPORTing Craig Ringer <craig@2ndquadrant.com>
Re: Random PGDLLIMPORTing Magnus Hagander <magnus@hagander.net>
Re: Random PGDLLIMPORTing Magnus Hagander <magnus@hagander.net>
On Thu, Nov 24, 2016 at 11:01 PM, Magnus Hagander  wrote:
> On Thu, Nov 24, 2016 at 2:58 PM, Craig Ringer  wrote:
> My guess is that PGDLLIMPORT has been added explicitly when somebody needed
> it for something, without any actual thought. I can't say I see any reason
> not to export the other ones as well -- more that maybe there are even more
> that are needed?

Yes, more or less. The reasoning behind at least the PostmasterPID bit is that:
https://www.postgresql.org/message-id/CAB7nPqS_=14KRCDcH6NyRsW8c58J1cwXv6QCVS7YP-6tTHQ1nA@mail.gmail.com
That resulted in cac83219.

The other ones could perhaps be marked with PGDLLIMPORT. Now usually
we need a use-case behind this change, and there are not that many
hackers on Windows doing much plugin development.
-- 
Michael


В списке pgsql-hackers по дате отправления
От: Pavel Stehule
Дата:
Сообщение: Re: patch: function xmltable
От: Robert Haas
Дата:
Сообщение: Re: UNDO and in-place update
FAQ