On Mon, Jan 11, 2010 at 2:00 AM, Michael Tenenbaum
> The following bug has been logged online:
> Bug reference: 5271
> Logged by: Michael Tenenbaum
> Email address: michael(at)strategic-techs(dot)com
> PostgreSQL version: 8.3.9
> Operating system: Gentoo Linux
> Description: pg_dump: schema with OID 22519 does not exist
> According to the posts I picked up from a Google search, this is a bug that
> never seems to get fixed.
> I followed Tom's advice and deleted entries in
> pg_type and pg_class
> and pg_dump is working ok.
> The object was a table in a development system with only a few entries.
> hardly anything was written to the table in the past few weeks, but the
> daily pg_dump was working fine until this evening.
Maybe I should be smarter than I am, but when you say that "this" is a
bug that never seems to get fixed, I'm not sure what "this" is. It
sounds like you're talking about system catalog corruption of some
sort, but without more details it's hard to speculate as to what might
Unfortunately, it also sounds like you've destroyed all the
evidence... I don't suppose you have a copy of a version of the
database where this is still broken?
In response to
pgsql-bugs by date
|Next:||From: Steve White||Date: 2010-01-11 16:41:07|
|Subject: BUG #5272: PL/Python SELECT: return composite fields as dict, not str|
|Previous:||From: Filip Rembiałkowski||Date: 2010-01-11 14:27:15|
|Subject: error after dropping column|