Turns out this was most likely the pg_upgrade bug. In our case, I was able
to dump and recreate the table in question. Since then, this has been made
public: http://wiki.postgresql.org/wiki/20110408pg_upgrade_fix
--
View this message in context:
http://postgresql.1045698.n5.nabble.com/could-no
Running 9.0.2 on Centos.
I just discovered this in my production error log. Starting about 45
minutes ago, I got 70 of these, within 2 seconds:
28652 2011-04-04 21:47:29 EDT [33]WARNING: PD_ALL_VISIBLE flag was
incorrectly set in relation "pg_toast_49338181" page 16820
These warnings were im
