On Tue, Apr 8, 2008 at 9:30 PM, Tom Lane <tgl@xxxxxxxxxxxxx> wrote:
I may have had a VACUUM FULL on some of my own tables but definitely not on any system tables. There was also a bunch (maybe 10) autovacuum processes working at that time.
Regards
Mikko
"Mikko Partio" <mpartio@xxxxxxxxx> writes:
> On Tue, Apr 8, 2008 at 6:38 PM, Zdenek Kotala <Zdenek.Kotala@xxxxxxx> wrote:
>> It is really strange. It would be nice to have reproduce scenario. Can youIs it possible that anything was doing a VACUUM FULL on pg_class
>> run same DDL command which invoke a catalog corruption on test database
>> cluster?
> I tried it on a fresh instance but it went through with no errors :(
concurrently with your schema changes on these tables? The behavior
looks suspiciously like some problems we've seen before wherein rows
ended up with the wrong commit-bit markings...
I may have had a VACUUM FULL on some of my own tables but definitely not on any system tables. There was also a bunch (maybe 10) autovacuum processes working at that time.
Regards
Mikko
