RE: [HACKERS] Threads
От | Ansley, Michael |
---|---|
Тема | RE: [HACKERS] Threads |
Дата | |
Msg-id | 1BF7C7482189D211B03F00805F8527F70ED0A6@S-NATH-EXCH2 обсуждение исходный текст |
Ответы |
Re: [HACKERS] Threads
|
Список | pgsql-hackers |
Aren't there cases, though, where multi-threading could be used within the back end design that we have at the moment, for example, to avoid lags during I/O? So, while the nth block of data is being read from the disk, the (n-1)th block is being processed by the next process down the line. For example... This wouldn't (shouldn't?) break the isolation that currently exists due to single-process servers. MikeA >> > As well, a few have been asking about multi-threading. >> > Any thoughts? >> >> Threads within a client backend might be interesting. imho a >> single-process multi-client multi-threaded server is just asking for >> trouble, putting all clients at risk for any single misbehaving one. >> Particularly with our extensibility features, where users and admins >> can add functionality through code they have written (or are >> trying to >> write ;) having each backend isolated is A Good Thing. >> >> istm that many of the cases for which multi-threading is >> proposed (web >> serving always comes up) can be solved using persistant >> connections or >> other techniques. >> >> - Thomas
В списке pgsql-hackers по дате отправления: