Tom Lane wrote:
> I wrote:
> > "Francisco Reyes" <[EMAIL PROTECTED]> writes:
> >> On 3:09 pm 05/28/08 Gregory Stark <[EMAIL PROTECTED]> wrote:
> > Does it really have a COPY command at the beginning? Are you really doing
> > >\i data/usb_t_60M.sql or were you trying to do a copy from this file?
>
I wrote:
> "Francisco Reyes" <[EMAIL PROTECTED]> writes:
>> On 3:09 pm 05/28/08 Gregory Stark <[EMAIL PROTECTED]> wrote:
> Does it really have a COPY command at the beginning? Are you really doing >\i
> data/usb_t_60M.sql or were you trying to do a copy from this file?
>> Argh..That's it.
>> When
"Francisco Reyes" <[EMAIL PROTECTED]> writes:
> On 3:09 pm 05/28/08 Gregory Stark <[EMAIL PROTECTED]> wrote:
>> Does it really have a COPY command at the beginning? Are you really doing
>> >\i data/usb_t_60M.sql or were you trying to do a copy from this file?
> Argh..That's it.
> When I re-organi
On Wed, May 28, 2008 at 03:42:47PM -0400, Francisco Reyes wrote:
> Is there a slowdown by keeping the debug RPM?
> Or should I only have it when trying to troubleshoot a problem?
Debug info costs nothing if its not being used.
Have a nice day,
--
Martijn van Oosterhout <[EMAIL PROTECTED]> ht
On 3:09 pm 05/28/08 Gregory Stark <[EMAIL PROTECTED]> wrote:
>Does it really have a COPY command at the beginning? Are you really doing >\i
>data/usb_t_60M.sql or were you trying to do a copy from this file?
Argh..That's it.
When I re-organized the scripts I must have taken the copy command from
"Francisco Reyes" <[EMAIL PROTECTED]> writes:
> #1 0x002a955820ae in pqPutMsgBytes (buf=0x2a9860a010, len=2147483647,
So it's trying to execute an sql query that's MAXINT bytes long which is
pretty off-course.
> #5 0x00406e95 in SendQuery (
> query=0x2a9860a010
> "yjbjK8WKLRH
On 11:09 am 05/28/08 Tom Lane <[EMAIL PROTECTED]> wrote:
Re-send. Didn't do reply-all before.
> Well, it would be if it were right; but PQsendQuery doesn't call
> PQunescapeBytea, so there's something wrong with the debug info.
..
> > compat-postgresql-libs-debuginfo-3-2PGDG.rhel4.x86_64.rpm
Th
On 11:09 am 05/28/08 Tom Lane <[EMAIL PROTECTED]> wrote:
> > I installed
> > compat-postgresql-libs-debuginfo-3-2PGDG.rhel4.x86_64.rpm
> > postgresql-debuginfo-8.2.7-1PGDG.rhel4.x86_64.rpm
>
> Do those *exactly* match the versions of the Postgres RPMs you're
> using?
I got them from the same di
"Francisco Reyes" <[EMAIL PROTECTED]> writes:
> (gdb) bt
> #0 0x003cc31723e6 in memcpy () from /lib64/tls/libc.so.6
> #1 0x00364bf0e0ae in PQunescapeBytea () from /usr/lib64/libpq.so.5
> #2 0x00364bf0e230 in PQunescapeBytea () from /usr/lib64/libpq.so.5
> #3 0x00364bf0c09e in PQ
On 6:28 pm 05/27/08 Tom Lane <[EMAIL PROTECTED]> wrote:
> Can you get us a stack trace from the crash?
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 182894175648 (LWP 4487)]
0x003cc31723e6 in memcpy () from /lib64/tls/libc.so.6
(gdb) bt
#0 0x003cc31723e6 in mem
"Francisco Reyes" <[EMAIL PROTECTED]> writes:
> I am setting up a new machine and preparing some standard benchmark tests.
> While trying to load some data using "copy from" psql is crashing.
Can you get us a stack trace from the crash? (You'd likely need to
install the postgresql-debuginfo RPM t
11 matches
Mail list logo
