Re: Phantom Command ID
От | Jim C. Nasby |
---|---|
Тема | Re: Phantom Command ID |
Дата | |
Msg-id | 20060920201304.GW28987@nasby.net обсуждение исходный текст |
Ответ на | Re: Phantom Command ID (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: Phantom Command ID
|
Список | pgsql-hackers |
On Wed, Sep 20, 2006 at 04:02:00PM -0400, Tom Lane wrote: > Heikki Linnakangas <heikki@enterprisedb.com> writes: > > A big question is, do we need to implement spilling to disk? > > My thought is no, at least not in the first cut ... this is something > that can be added later if it proves critical, and right at the moment > my guess is that it never will. The data structure design sounds fine. What would the failure mode be? Would we just keep going until the box ran out of memory? I think it'd be better to have some kind of hard limit so that a single backend can't grind a production server into a swap-storm. (Arguably, not having a limit is exposing a DoS vulnerability). -- Jim Nasby jim@nasby.net EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)
В списке pgsql-hackers по дате отправления: