Re: Phantom Command ID - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Phantom Command ID
Date
Msg-id 19549.1158788620@sss.pgh.pa.us
Whole thread Raw
In response to Re: Phantom Command ID  ("Jim C. Nasby" <jim@nasby.net>)
List pgsql-hackers
"Jim C. Nasby" <jim@nasby.net> writes:
> I didn't realize we had a lot of ways a backend could run a machine out
> of memory, or at least ways that didn't have some kind of limit (ie:
> work_mem). Are any of them very easy to run into?

work_mem has nothing to do with trying to guarantee "no swapping DoS".
If it did, it wouldn't be USERSET, and it wouldn't be per query step.
The fact is that ulimit does what you want in that regard already;
why should we try to reinvent that wheel?
        regards, tom lane


pgsql-hackers by date:

Previous
From: "Jim C. Nasby"
Date:
Subject: Re: Phantom Command ID
Next
From: "Jim C. Nasby"
Date:
Subject: Re: [PATCHES] Incrementally Updated Backup