| From: | Steve Atkins <steve(at)blighty(dot)com> |
|---|---|
| To: | SF PostgreSQL <sfpug(at)postgresql(dot)org> |
| Subject: | Re: IN question |
| Date: | 2008-12-10 22:12:10 |
| Message-ID: | 2DDBF020-874B-4A0D-9A2B-BBAE20BC0936@blighty.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | sfpug |
On Dec 10, 2008, at 2:08 PM, A. Elein Mustain wrote:
> On Wed, Dec 10, 2008 at 01:41:01PM -0800, Josh Berkus wrote:
>> Steve,
>>
>>> I'm not so sure there's such a thing as a limit that's too big.
>>
>> Sure there is. out-of-memory error.
>>
>> Actually, I'd like to see the limit set at work_mem.
>>
>> --Josh
>>
>
> I write big, long queries everyday. I would prefer the
> default be no limit but out of memory. If you must add
> a limit (why????) then it should NOT be the default.
Well, one reason for a limit is to provide the DBA with a
last line of defense against idiot clients. Given some of
the dumb things automated query builders and ORMs
are prone to do that's not such a bad idea.
Cheers,
Steve
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Meredith L. Patterson | 2008-12-10 22:34:02 | Re: IN question |
| Previous Message | A. Elein Mustain | 2008-12-10 22:08:24 | Re: IN question |