Re: Performance degradation in commit ac1d794
От | Tom Lane |
---|---|
Тема | Re: Performance degradation in commit ac1d794 |
Дата | |
Msg-id | 29091.1452786360@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: Performance degradation in commit ac1d794 (Robert Haas <robertmhaas@gmail.com>) |
Ответы |
Re: Performance degradation in commit ac1d794
|
Список | pgsql-hackers |
Robert Haas <robertmhaas@gmail.com> writes: > Incidentally, if we're going to whack around the latch API, it would > be nice to pick a design which wouldn't be too hard to extend to > waiting on multiple sockets. The application I have in mind is to > send of queries to several foreign servers at once and then wait until > bytes come back from any of them. It's mostly pie in the sky at this > point, but it seems highly likely to me that we'd want to do such a > thing by waiting for bytes from any of the sockets involved OR a latch > event. Instead of SetSocketToWaitOn, maybe AddSocketToWaitSet and RemoveSocketFromWaitSet? And you'd need some way of identifying which socket came ready after a wait call... regards, tom lane
В списке pgsql-hackers по дате отправления: