| From: | Willy-Bas Loos <willybas(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Sam Mason <sam(at)samason(dot)me(dot)uk>, pgsql-general(at)postgresql(dot)org, mmoncure(at)gmail(dot)com, sss(at)clearsenses(dot)com |
| Subject: | Re: where does postgres keep the query result until it is returned? |
| Date: | 2010-09-20 14:06:35 |
| Message-ID: | AANLkTimLmpP1SwFgiUjXJmt6vEj1jsdDURrHYbQbCkvK@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
>>> 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.
>
>> ?? I hear that it's posible to store up to a GiB as a value for a "text" field.
>> How would i possibly retrieve that data from the database?
>
> That's the *theoretical* limit. In a 32-bit build, the practical limit
> is going to be quite a bit less.
Sheesh..
- why?
- how about 64 bit?
- should this be documented?
--
"Patriotism is the conviction that your country is superior to all
others because you were born in it." -- George Bernard Shaw
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thom Brown | 2010-09-20 14:08:39 | Re: Alter Table Auto_Increment |
| Previous Message | Carlos Mennens | 2010-09-20 13:53:34 | Alter Table Auto_Increment |