| From: | "Jim C(dot) Nasby" <jim(at)nasby(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Heikki Linnakangas <heikki(at)enterprisedb(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Phantom Command ID |
| Date: | 2006-09-20 20:13:04 |
| Message-ID: | 20060920201304.GW28987@nasby.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Sep 20, 2006 at 04:02:00PM -0400, Tom Lane wrote:
> Heikki Linnakangas <heikki(at)enterprisedb(dot)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(at)nasby(dot)net
EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Martijn van Oosterhout | 2006-09-20 20:14:10 | Re: TODO: Fix CREATE CAST on DOMAINs |
| Previous Message | Tom Lane | 2006-09-20 20:08:53 | Re: TODO: Fix CREATE CAST on DOMAINs |