Jacky Leng wrote:
Asserts on data-consistency checks aren't really a good idea.
(IOW this is "can't happen" only as long as your database isn't
corrupt...)
Then why not change this to an "ereport(PANIC ...)"?
If you have a corrupted database, you want to be able to read it, not
panic. If anything, we could put a WARNING there, but I'm not 100% sure
it really is a "can't happen" case.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
