hmm - I don't suppose the RHEL builds already include your patch against this issue? If so I guess it would be useful to know :)
I've run through the steps you outlined to reproduce the fault on a new box (after having reproduced it successfully on test servers), and it does not show the problem:
[root@XXXXXXX data]# !psql
psql test -U XXXXX
Welcome to psql 8.3.0, the PostgreSQL interactive terminal.
psql test -U XXXXX
Welcome to psql 8.3.0, the PostgreSQL interactive terminal.
Type: \copyright for distribution terms
\h for help with SQL commands
\? for help with psql commands
\g or terminate with semicolon to execute query
\q to quit
\h for help with SQL commands
\? for help with psql commands
\g or terminate with semicolon to execute query
\q to quit
test=# create table foo as select null::int as x from generate_series(1,2000) x;
SELECT
test=# delete from foo;
DELETE 2000
test=# select count(*) from foo;
count
-------
0
(1 row)
SELECT
test=# delete from foo;
DELETE 2000
test=# select count(*) from foo;
count
-------
0
(1 row)
test=# vacuum full foo;
VACUUM
test=#
test=# set debug_assertions to on;
ERROR: assertion checking is not supported by this build
test=#
VACUUM
test=#
test=# set debug_assertions to on;
ERROR: assertion checking is not supported by this build
test=#
The RPMs installed from are these:
postgresql-8.3.0-1PGDG.rhel4
postgresql-libs-8.3.0-1PGDG.rhel4
postgresql-server-8.3.0-1PGDG.rhel4
postgresql-libs-8.3.0-1PGDG.rhel4
postgresql-server-8.3.0-1PGDG.rhel4
Thanks
Shane
From: Tom Lane [mailto:tgl@xxxxxxxxxxxxx]
Sent: Fri 29/02/2008 22:55
To: Shane Wright
Cc: pgsql-general@xxxxxxxxxxxxxx
Subject: Re: Upgrade to 8.3.0?
"Shane Wright" <shane.wright@xxxxxxxxxxxxxxxxxxxx> writes:
> I'm assuming that the default RPMs for RHEL 4 (on ftp.postgresql.org) are not built with --enable-cassert - and that I can veryify this by using the same reproduction case you demonstrated in the bug history?
I believe they aren't, but you could check by seeing what pg_config
reports as the configure options; or even more directly by seeing if
it will let you "SET debug_assertions TO on".
regards, tom lane