"Catalog corruption" - Search results in mailing lists
Mailing lists >> pgsql-bugs >> Thread
2024-12-07 01:51:42 | Re: Dangling operator family after DROP TYPE (Tom Lane)
catalog corruption that could occur due to old bugs. + */ + /*------ translator: %d is the operator strategy
Mailing lists >> pgsql-bugs >> Thread
2024-02-27 18:14:43 | Re: BUG #18367: Cannot drop schema (Tom Lane)
original. If you've found one bit of catalog corruption there's likely more. regards, tom lane
Mailing lists >> pgsql-bugs >> Thread
2022-10-17 14:41:35 | Re: BUG #17646: create rule named "_RETURN" will cause pg core (Tom Lane)
catalog corruption. In versions before v12, I get something like regression=# select * from v1; ERROR
Mailing lists >> pgsql-bugs >> Thread
2022-02-19 07:04:14 | Re: Report some potential memory leak bugs in pg_dump.c (Tom Lane)
with a catalog-corruption scenario for the non-cached path to be taken. regards, tom lane
Mailing lists >> pgsql-bugs >> Thread
2020-04-14 18:00:19 | Re: [bug] Table not have typarray when created by single user mode (Alvaro Herrera)
catalog corruption?) -- Álvaro Herrera https://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training
Mailing lists >> pgsql-bugs >> Thread
2019-03-08 11:00:40 | Re: BUG #15631: Generated as identity field in a temporary table withon commit drop corrupts (Peter Eisentraut)
catalog corruption that will cause a later test to fail.) We can leave it in the archive
Mailing lists >> pgsql-bugs >> Thread
2018-08-03 20:29:54 | Re: BUG #15309: ERROR: catalog is missing 1 attribute(s) for relid760676 when max_parallel (Peter Geoghegan)
catalog corruption. I recall repairing pg_attribute by hand when this happened, and then having
Mailing lists >> pgsql-bugs >> Thread
2015-12-17 20:22:02 | Re: BUG #9923: "reassign owned" does not change permissions grantor (Tom Lane)
catalog corruption later seems to trump that argument. Actually, I guess we should take out that
Mailing lists >> pgsql-bugs >> Thread >> Search in thread (2)
2014-03-10 12:40:23 | Re: BUG #9472: pg_dumpall fails with "unrecognized node type: 650" (Weiss, Wilfried)
catalog corruption, but I don't see how that would explain this particular symptom. I wonder
Mailing lists >> pgsql-bugs >> Thread
2012-04-30 13:41:26 | Re: 9.1.3 backends getting stuck in 'startup' (Jeff Frost)
initdb'd original server, the problem has not recurred. Maybe the problem was catalog corruption?
Mailing lists >> pgsql-bugs >> Thread
2010-06-13 20:49:43 | Re: BUG #5504: cache lookup failed for function (Tom Lane)
catalog corruption, or it might mean there is something wrong with your postgres executable. Can you do the command
Mailing lists >> pgsql-bugs >> Thread
2010-01-11 10:38:49 | Re: BUG #5271: pg_dump: schema with OID 22519 does not exist (Robert Haas)
catalog corruption of some sort, but without more details it's hard to speculate as to what
Mailing lists >> pgsql-bugs >> Thread
2009-07-20 19:50:06 | BUG #4929: Corrupted pg_class, possibly truncate/rollback related (Robert Treat)
catalog corruption. The problems started with a failing pg_dump... pg_dump: SQL command failed
Mailing lists >> pgsql-bugs >> Thread
2009-02-20 15:41:59 | Re: BUG #4669: pg_dump reports error about multiple rows (Tom Lane)
catalog corruption issues to me. Have you had any system crashes lately? Are you sure