| From: | Sandeep Srinivasa <sss(at)clearsenses(dot)com> |
|---|---|
| To: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
| Cc: | Sam Mason <sam(at)samason(dot)me(dot)uk>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: where does postgres keep the query result until it is returned? |
| Date: | 2010-09-20 12:09:00 |
| Message-ID: | AANLkTikiyXgHd8Wjub+=pgjEGfMuykcw11oNa8X3zAKU@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Mon, Sep 20, 2010 at 5:27 PM, Merlin Moncure <mmoncure(at)gmail(dot)com> wrote:
> On Fri, Sep 17, 2010 at 3:59 PM, Sam Mason <sam(at)samason(dot)me(dot)uk> wrote:
> > On Fri, Sep 17, 2010 at 04:51:46PM +0200, Willy-Bas Loos wrote:
> >> i have a function that produces a result in xml.
> >> that is one row, one value even, but it grows pretty large.
> >> how is that handled?
> >
> > Rows are sent back in the entireity, so the PG instance would need
> > enough memory to work with that row. When you're running a 32bit
> > version of PG, values whose size is beyond ~100MB are a bit touch and go
> > whether it will work.
>
Is'nt "work_mem" used for this on the server side (when sorts and
hash-tables are required) and "temp_buffers" (when temporary tables are
created) ?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Eric Ndengang | 2010-09-20 12:31:22 | unexpected EOF on client connection |
| Previous Message | Merlin Moncure | 2010-09-20 11:57:09 | Re: where does postgres keep the query result until it is returned? |