Teodor Sigaev [EMAIL PROTECTED] writes:
It seems to me last run
(http://pgbuildfarm.org/cgi-bin/show_log.pl?nm=dugongdt=2007-09-11%2016:05:01)
points to problem with hash implementation.
SELECT to_tsvector('thesaurus_tst', 'one postgres one two one two three
one');
+ NOTICE:
Tom Lane wrote:
Teodor Sigaev [EMAIL PROTECTED] writes:
It seems to me last run
(http://pgbuildfarm.org/cgi-bin/show_log.pl?nm=dugongdt=2007-09-11%2016:05:01)
points to problem with hash implementation.
SELECT to_tsvector('thesaurus_tst', 'one postgres one two one two three
one');
Stefan Kaltenbrunner [EMAIL PROTECTED] writes:
Tom Lane wrote:
Teodor Sigaev [EMAIL PROTECTED] writes:
It seems to me last run
(http://pgbuildfarm.org/cgi-bin/show_log.pl?nm=dugongdt=2007-09-11%2016:05:01)
points to problem with hash implementation.
SELECT
Sergey E. Koposov [EMAIL PROTECTED] writes:
It turned out that the offending assert is
Assert(BgWriterShmem != NULL); in bgwriter.c:990
After commenting it out everything works.
That's simply bizarre ...
Also, I tried to add 'volatile' to the declaration of BgWriterShmem. After
that the
On Tue, 11 Sep 2007, Tom Lane wrote:
Well, the first thing I'd suggest is trying to localize which Assert
makes it fail. From the bug's behavior I think it is highly probable
that the problem is in fsync signalling, which puts it either in
bgwriter.c or md.c. Try recompiling those modules
On Tue, 11 Sep 2007, Tom Lane wrote:
dugong has been failing contribcheck repeatably for the last day or so,
with a very interesting symptom: CREATE DATABASE is failing with
The reason for that is that I've been trying to switch from 9.1 to 10.0
version of the ICC compiler. A month ago, I've
Sergey E. Koposov [EMAIL PROTECTED] writes:
On Tue, 11 Sep 2007, Tom Lane wrote:
dugong has been failing contribcheck repeatably for the last day or so,
with a very interesting symptom: CREATE DATABASE is failing with
The reason for that is that I've been trying to switch from 9.1 to 10.0
This could be a compiler bug, or it could be our fault --- might need
a volatile on some pointer or other, for example, to prevent the
compiler from making an otherwise legitimate assumption. So it seems
worth chasing it down.
Tom, Thank you for the directions, I'll try to do what you
Sergey E. Koposov [EMAIL PROTECTED] writes:
BTW, does ICC have any switch corresponding to gcc's -fno-strict-aliasing?
I see that configure tries to feed that switch to it, but it might
want some other spelling.
Apparently in none of the ICC manuals -fno-strict-aliasing is described,
but
Well, the first thing I'd suggest is trying to localize which Assert
makes it fail. From the bug's behavior I think it is highly probable
that the problem is in fsync signalling, which puts it either in
bgwriter.c or md.c. Try recompiling those modules separately without
cassert (leaving all
Actually, in the log file I also see some messages about has_seq_search:
КОМАНДА: CREATE DATABASE contrib_regression TEMPLATE=template0
NOTICE: database contrib_regression does not exist, skipping
ERROR: too many active hash_seq_search scans
ERROR: too many active hash_seq_search scans
Sergey E. Koposov [EMAIL PROTECTED] writes:
Actually, in the log file I also see some messages about has_seq_search:
=EB=EF=ED=E1=EE=E4=E1: CREATE DATABASE contrib_regression TEMPLATE=3Dtem=
plate0
NOTICE: database contrib_regression does not exist, skipping
ERROR: too many active
Sergey E. Koposov [EMAIL PROTECTED] writes:
Actually, in the log file I also see some messages about has_seq_search:
ERROR: too many active hash_seq_search scans
ERROR: too many active hash_seq_search scans
ERROR: too many active hash_seq_search scans
BTW, I just made a commit to include
It seems to me last run
(http://pgbuildfarm.org/cgi-bin/show_log.pl?nm=dugongdt=2007-09-11%2016:05:01)
points to problem with hash implementation.
*** ./expected/tsdicts.out Tue Sep 11 20:05:23 2007
--- ./results/tsdicts.out Tue Sep 11 20:18:38 2007
***
*** 301,306
Teodor Sigaev [EMAIL PROTECTED] writes:
It seems to me last run
(http://pgbuildfarm.org/cgi-bin/show_log.pl?nm=dugongdt=2007-09-11%2016:05:01)
points to problem with hash implementation.
dynahash.c is used all over the system, though. If it were broken by a
compiler issue, it's hard to
On Tue, 11 Sep 2007, Tom Lane wrote:
NOTICE: database contrib_regression does not exist, skipping
ERROR: too many active hash_seq_search scans
ERROR: too many active hash_seq_search scans
ERROR: too many active hash_seq_search scans
ERROR: too many active hash_seq_search scans
With
Sergey E. Koposov [EMAIL PROTECTED] writes:
On Tue, 11 Sep 2007, Tom Lane wrote:
NOTICE: database contrib_regression does not exist, skipping
ERROR: too many active hash_seq_search scans
ERROR: too many active hash_seq_search scans
ERROR: too many active hash_seq_search scans
ERROR: too
On Tue, 11 Sep 2007, Tom Lane wrote:
Sergey E. Koposov [EMAIL PROTECTED] writes:
On Tue, 11 Sep 2007, Tom Lane wrote:
NOTICE: database contrib_regression does not exist, skipping
ERROR: too many active hash_seq_search scans
ERROR: too many active hash_seq_search scans
ERROR: too many
Sergey E. Koposov [EMAIL PROTECTED] writes:
Yes, indeed. After several make installcheck's
I get
ERROR: too many active hash_seq_search scans, cannot start one on smgr
relation table
ERROR: too many active hash_seq_search scans, cannot start one on smgr
relation table
Hm, so that must
Sergey E. Koposov wrote:
With hash_seq_search ERROR, it was partially a false alarm. I've had
some old postgres daemon hanging around and writing that to the log.
Although I remember seeing that hash_seq_search message recently when
dealing with this bug, it does not show up in the course
On Tue, 11 Sep 2007, Andrew Dunstan wrote:
Your buildfarm member must be seriously misconfigured if you can get the logs
from different postmasters comingled. Every run gets its own logfile in its
own inst directory.
No, everything I'm doing now about that bug, I'm doing in the very
dugong has been failing contribcheck repeatably for the last day or so,
with a very interesting symptom: CREATE DATABASE is failing with
ERROR: could not fsync segment 0 of relation 1663/40960/41403: No such file or
directory
ERROR: checkpoint request failed
HINT: Consult recent messages in
22 matches
Mail list logo
