From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Féliciano Matias <feliciano(dot)matias(at)free(dot)fr> |
Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: psql and bytea |
Date: | 2003-05-15 14:47:53 |
Message-ID: | 8509.1053010073@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
=?ISO-8859-1?Q?F=E9liciano?= Matias <feliciano(dot)matias(at)free(dot)fr> writes:
> one=3D> -- this is not the original size (20M : 20971520).
> I don't have any problems with smaller files (10Mo is always fine).
> All of this is used with postgresql 7.3.2 shipped with Red Hat Linux 9 .
Hmm. There used to be some off-by-one type bugs in psql's
variable-substitution code, but those were fixed long before 7.3.2.
In any case, it's hard to see why such a problem would only arise
when you got past 10Mb string lengths.
I couldn't duplicate the problem here, so I'm going to suggest that
maybe you have a hardware problem? Perhaps there's a flaky RAM chip in
an area of memory that doesn't get used until you push up the size
of psql quite a bit. It'd be worth running memtest86 for awhile to
check.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Johnson, Shaunn | 2003-05-15 14:54:01 | sql and timestamp variable |
Previous Message | scott.marlowe | 2003-05-15 14:45:16 | Re: TESTING the DATABASE |