pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Gnanakumar <gnanam@zoniac.com>
To: 'Rosser Schwarz' <rosser.schwarz@gmail.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: PSQLException: ERROR: could not open relation with OID xxxx
Date: Tue, 15 Mar 2011 10:16:44 +0530
Message-ID: <002001cbe2cb$fda09870$f8e1c950$@com> (raw)
In-Reply-To: <AANLkTimxMm_PcachrqvOBeWwh_c7_CLJd2qhBj3t_7vx@mail.gmail.com>
References: <006d01cbdfd5$f48becb0$dda3c610$@com>
	<4D79FF3D020000250003B7C6@gw.wicourts.gov>
	<004f01cbe20c$f2c6a260$d853e720$@com>
	<AANLkTikOgLeit=eTEtin-+XX8Rb9rKbwahuUy62q3TBf@mail.gmail.com>
	<006201cbe21c$8a657e20$9f307a60$@com>
	<AANLkTimxMm_PcachrqvOBeWwh_c7_CLJd2qhBj3t_7vx@mail.gmail.com>

> The key to understanding the problem is to realize that system
> catalogs are pretty much regular tables in PostgreSQL, with some
> additional special rules (no triggers, can't be CLUSTERed or ALTERed,
> &c).  Anything you'd do in a regular table that would create a dead
> tuple — UPDATEs, DELETEs, &c — will have the same effect on a catalog.

Thanks for the detailed explanation on this topic.




view thread (11+ messages)  latest in thread

Message-ID: <002001cbe2cb$fda09870$f8e1c950$@com>
Permalink:  ../002001cbe2cb$fda09870$f8e1c950$@com/
Also on:    postgresql.org/message-id/002001cbe2cb$fda09870$f8e1c950$@com

 · 

reply
Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-admin@postgresql.org
  Cc: gnanam@zoniac.com, rosser.schwarz@gmail.com
  Subject: Re: PSQLException: ERROR: could not open relation with OID xxxx
  In-Reply-To: <002001cbe2cb$fda09870$f8e1c950$@com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox