Re: pg_hba.conf: samehost and samenet [REVIEW]
От | Magnus Hagander |
---|---|
Тема | Re: pg_hba.conf: samehost and samenet [REVIEW] |
Дата | |
Msg-id | 9837222c0909230246t240771dcr21d6845d922c4c16@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: pg_hba.conf: samehost and samenet [REVIEW] (Stef Walter <stef-list@memberwebs.com>) |
Ответы |
Re: pg_hba.conf: samehost and samenet [REVIEW]
Re: pg_hba.conf: samehost and samenet [REVIEW] |
Список | pgsql-hackers |
On Mon, Sep 21, 2009 at 20:12, Stef Walter <stef-list@memberwebs.com> wrote: <snip> > Updated in attached patch. This patch does not build on Windows, the error is: ip.obj : error LNK2019: unresolved external symbol __imp__WSAIoctl@36 referencedin function _pg_foreach_ifaddr ip.obj : error LNK2019: unresolved external symbol __imp__WSASocketA@24 referenc ed in function _pg_foreach_ifaddr .\Release\libpq\libpq.dll : fatal error LNK1120: 2 unresolved externals I don't have time to investigate this further right now, so if somebody else want to dig into why that is happening that would be helpful :) Also, one thought - with samenet we currently from what I can tell enumerate all interfaces. Not just those we bind to based on listen_addresses. Is that intentional, or should we restrict us to subnets reachable through the interfaces we're actually listening on? -- Magnus HaganderMe: http://www.hagander.net/Work: http://www.redpill-linpro.com/
В списке pgsql-hackers по дате отправления: