Tatsuo Ishii [EMAIL PROTECTED] writes:
The bit test diffs seem to indicate that bit_cmp is messed up. That
depends on memcmp. I seem to recall something about memcmp not being
8-bit-clean on SunOS ... does that ring a bell with anyone?
Good point. From the man page of memcmp(3) on this
Vince Vielhaber [EMAIL PROTECTED] writes:
On 22 Mar 2001, Trond Eivind [iso-8859-1] Glomsrd wrote:
[EMAIL PROTECTED] (Trond Eivind Glomsrd) writes:
Thomas Lockhart [EMAIL PROTECTED] writes:
If a platform you are running on is not listed, make sure it gets
included!
Red
On 23 Mar 2001, Trond Eivind [iso-8859-1] Glomsrød wrote:
Vince Vielhaber [EMAIL PROTECTED] writes:
On 22 Mar 2001, Trond Eivind [iso-8859-1] Glomsrød wrote:
[EMAIL PROTECTED] (Trond Eivind Glomsrød) writes:
Thomas Lockhart [EMAIL PROTECTED] writes:
If a platform you are
Recent changes in pg_crc.c (64 bit CRC) introduced non
portable constants of the form:
-c -o pg_crc.o pg_crc.c
287 | 0x, 0x42F0E1EBA9EA3693,
a..
a - 1506-207 (W) Integer constant
Zeugswetter Andreas SB [EMAIL PROTECTED] writes:
I'm aware that some compilers will produce warnings about these
constants, but there should not be any that fail completely, since
(a) we won't be compiling this code unless we've proven that the
compiler supports a 64-bit-int datatype, and
Postgre 7.0.3, on RedHat Linux 6.2 stock 2.2.16 kernel. Nothing special I
can think of, this server has been up and in use for the last 128 days with
no problem. Last night while cron was performing the nightly vacuuming of
all databases on one of our servers, I got this from cron.
Vacuuming
I have since stopped the database server and all my users are
dead in the water at the moment. I took postgres down to single
user mode and I'm doing a vacuum and was considering doing an
iccpclean. Any other suggestions? dump restore?
Any Idea what happened?
Drop indices; vacuum; create
Postgre 7.0.3, on RedHat Linux 6.2 stock 2.2.16 kernel. Nothing special I
can think of, this server has been up and in use for the last 128 days
with
no problem. Last night while cron was performing the nightly vacuuming of
all databases on one of our servers, I got this from cron.
I'm aware that some compilers will produce warnings about these
constants, but there should not be any that fail completely, since
(a) we won't be compiling this code unless we've proven that the
compiler supports a 64-bit-int datatype, and
Unfortunately configure does not check the
OpenBSD 2.8 x867.1 2001-03-22, Brandon. Palmer
OBSD checks out for sparc and i386. We did need to make a change to the
resultmap file to make the regression tests clean for the sparc. I have
attached the diff.
Also, on the sparc that i'm using (sparc4/110), make check takes 1950
Matthew [EMAIL PROTECTED] writes:
FYI now when I try to use psql to connect to the database I get this
error:
bash$ psql cms
psql: FATAL 1: cannot find attribute 1 of relation pg_trigger
So the indexes on pg_attribute are hosed too. I wonder whether that was
the original
The vacuum I tried in single user mode failed (froze on a
table, for over 20 minutes) so I killed it.
Did you destroy indices before vacuum?
Not all of them, it's a large database and I am trying
to get it up and running asap.
Did you destroy *all* indices of table vacuum hung
Matthew [EMAIL PROTECTED] writes:
FYI now when I try to use psql to connect to the database I get this
error:
bash$ psql cms
psql: FATAL 1: cannot find attribute 1 of relation pg_trigger
So the indexes on pg_attribute are hosed too. I wonder whether that was
the
The vacuum I tried in single user mode failed (froze on a
table, for over 20 minutes) so I killed it.
Did you destroy indices before vacuum?
Not all of them, it's a large database and I am trying to get it up
and running asap.
FYI now when I try to use psql to connect to
The vacuum I tried in single user mode failed (froze on a
table, for over 20 minutes) so I killed it.
Did you destroy indices before vacuum?
Vadim
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
What do you mean by the whole database? I have already
executed:
reindex database cms force
reindex table cases force
reindex table cases force
reindex table hits force
reindex table history force (and a few more)
How do I get it do reindex
bpalmer [EMAIL PROTECTED] writes:
seconds. Most of the time is spent in this test:
parallel group (13 tests): float4 int2 int4 text name varchar oid boolean
char float8 int8 bit numeric
There is a long pause between 'bit' and 'numeric'. Same with on i386. Is
this a problem that is
The Hermit Hacker [EMAIL PROTECTED] writes:
I'm going to hold off on a formal announcement to -announce until tomorrow
evening, to give the mirrors a chance to update, but if anyone would like
to download and run through the package, make sure all looks okay, its
available in the dev
Are we ready to start freezing docs? I'll assume that the tutorial
sections can freeze first, and that the admin sections will freeze last
(to get the latest platform support info).
Any preference on order, and does anyone have more docs changes in the
pipe? If so, we had better plan on doing
Hi all,
I've built 7.1beta6 on a number of different HP-UX platforms (11.00 32
bit, 11.00 64 bit, 11i 32 bit).
1. On all these platforms 'make check' hung. Since that's not
critical to whether PostgreSQL works or not I worked around it by
using a different shell:
gmake
Giles Lean [EMAIL PROTECTED] writes:
I'll look at this next week. If someone can confirm that
/usr/bin/sh works for make check on HP-UX 10.20 that would be
useful.
It does not work. See FAQ_HPUX.
2. I saw two different sets of output for geometry.out. These seem to
relate to
Giles Lean [EMAIL PROTECTED] writes:
It does not work. See FAQ_HPUX.
I'm confused: I don't see anything about shells or make check hanging
in doc/FAQ_HPUX. There is clear instruction to use GNU make, which I
am doing.
Hm, I thought I had updated that before beta6. What it has now is
The
I'll look at this next week. If someone can confirm that
/usr/bin/sh works for make check on HP-UX 10.20 that would be
useful.
It does not work. See FAQ_HPUX.
I'm confused: I don't see anything about shells or make check hanging
in doc/FAQ_HPUX. There is clear instruction
23 matches
Mail list logo
