Many thanks :)
I've tried to find this out for myself but have failed :(
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 should just get the memory allocation error on attempting to vacuum full - instead of an assertion failing and bringing down the whole PostgreSQL server (panic?))
Please could you confirm my assertion (sic) is correct?
(I get this behaviour on my test server and all appears to be ok)
From: Tom Lane [mailto:tgl(at)sss(dot)pgh(dot)pa(dot)us]
Sent: Fri 29/02/2008 19:46
To: Shane Wright
Subject: Re: [GENERAL] Upgrade to 8.3.0?
Shane Wright writes:
> - Is the HOT/VACUUMFULL bug above dangerous or is its biggest
> side-effect an error until a non-full vacuum is run?
As long as you don't build with --enable-cassert, that bug isn't real
nasty. Especially if you don't do VACUUM FULL routinely ;-)
regards, tom lane
In response to
pgsql-general by date
|Next:||From: Thomas Kellerer||Date: 2008-02-29 21:55:12|
|Subject: Re: pgsql structure export to XML|
|Previous:||From: fredj132||Date: 2008-02-29 21:01:02|
|Subject: Problems making client perl connection to postgres server|