Skip site navigation (1) Skip section navigation (2)

Re: [HACKERS] Another nasty cache problem

From: Patrick Welche <prlw1(at)newn(dot)cam(dot)ac(dot)uk>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: [HACKERS] Another nasty cache problem
Date: 2000-01-31 19:13:56
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
Tom Lane wrote:
> I'm down to the point where the parallel tests mostly work with a small
> SI buffer --- but they do still sometimes fail.

Have you committed your changes? I tried the parallel tests with cvs of around
5pm GMT 31 Jan, and they were all fine (I just ran out of procs at one point).
This is much better than last week! Thanks! I also tried that nonsensical
join from the other day, and it failed in the same way again:

newnham=# select * from crsids,"tblPerson" where
newnham-# crsids.crsid != "tblPerson"."CRSID";
Backend sent B message without prior T
D21Enter data to be copied followed by a newline.
End with a backslash and a period on a line by itself.

After \. :

Unknown protocol character 'M' read from backend.  (The protocol character is the first character the backend sends in response to a query it receives).
PQendcopy: resetting connection
Asynchronous NOTIFY 'ndropoulou' from backend with pid '1818589281' received.
Asynchronous NOTIFY 'ndropoulou' from backend with pid '1818589281' received.

pq_flush: send() failed: Broken pipe
FATAL: pq_endmessage failed: errno=32

but no NOTICEs about SI anywhere any more, in fact no messages at all until
the "Unknown protocol character" bit above. The psql frontend process grows to
about 120Mb in size before this if that matters (200Mb swap free).

(Looking at why pg_dumpall creates unique indices for each different type
of index at the moment...)



In response to


pgsql-hackers by date

Next:From: Ed LoehrDate: 2000-01-31 20:05:36
Subject: Re: [HACKERS] float4 confused as int??
Previous:From: Ed LoehrDate: 2000-01-31 18:37:44
Subject: Re: [HACKERS] float4 confused as int??

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group