From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Sam Mason <sam(at)samason(dot)me(dot)uk> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: literal limits in 8.3 |
Date: | 2008-11-24 15:45:42 |
Message-ID: | 1970.1227541542@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
Sam Mason <sam(at)samason(dot)me(dot)uk> writes:
> It's a normal 32bit Intel Debian system, nothing much special done
> to increase the kernel/user split or anything like that as far as I
> remember on this box. If I try with larger sizes it falls over with
> "out of memory", but up until around 755MB (760MB fails) it gives back
> "INSERT 0 1" which I've always read as inserting a row. A select on the
> table gives this inserted row containing a zero length string.
Well, I can't reproduce that here. Something strange about your
configuration maybe?
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Jaime Casanova | 2008-11-24 16:43:41 | filter statements in logs |
Previous Message | Dave Page | 2008-11-24 15:08:21 | Re: mail list traffic |
From | Date | Subject | |
---|---|---|---|
Next Message | Heikki Linnakangas | 2008-11-24 15:55:08 | Re: Visibility map, partial vacuums |
Previous Message | Tom Lane | 2008-11-24 15:44:40 | Re: [PATCHES] Solve a problem of LC_TIME of windows. |