Good morning,

We use postgresql 7.3.2 under Linux Red Hat 9.0.
We periodically dump and restore our database. I don't know if an error
occured during a dump restore but our DB seems to be corrupted.
Our base contains many pair of table with the same name.

Schema are the same = public.
How is it possible and how can i turn around this problem to have a
healthy DB.

Thank you.


<PRE>
<font face="sans-serif">
<table border=0 width=100%>
<tr><td><p lang="fr" style="color:green;font-size:x-small">Pensez &agrave; l'environnement : avez-vous besoin d'imprimer ce message ?</p></td></tr>
<tr><td><p lang-"en" style="color:green;font-size:x-small">Think environment : Do you need to print message ?</p></td></tr>
<tr><td><p lang="en" style="color:white;font-size:x-small">.</p></td></tr>
<tr><td><p lang="fr" style="font-size:x-small">Ce courrier &eacute;lectronique, et &eacute;ventuellement ses pi&egrave;ces jointes, peuvent contenir des informations confidentielles et/ou personnelles et a &eacute;t&eacute; envoy&eacute; uniquement &agrave; l'usage de la personne ou de l'entit&eacute; cit&eacute;e ci-dessus. Si vous receviez ce courrier &eacute;lectronique par erreur, merci de bien vouloir en avertir l'exp&eacute;diteur imm&eacute;diatement par la r&eacute;ponse en retour &agrave; ce courrier et effacer l'original et d&eacute;truire toute copie enregistr&eacute;e dans un ordinateur, ou imprim&eacute;e ou encore sauvegard&eacute;e sur un disque . Toute revue, retransmission ou toute autre forme d'utilisation de ce courrier &eacute;lectronique par toute autre personne que le destinataire pr&eacute;vue est strictement interdite.</p></td></tr>
<tr><td><p lang="fr" style="font-size:x-small">L'internet ne permettant pas d'assurer l'int&eacute;grit&eacute; de ce message, l'exp&eacute;diteur d&eacute;cline toute responsabilit&eacute; au cas o&ugrave; il aurait &eacute;t&eacute; intercept&eacute; ou modifi&eacute; par quiconque.</p></td></tr>
<tr><td><p lang="en" style="font-size:x-small">This e-mail and possibly any attachment may contain confidential and/or privileged information and is intended only for the use of the individual or entity named above. If you have received it in error, please advise the sender immediately by reply e-mail and delete and destroy all copies including all copies stored in the recipient's computer, printed or saved to disk. . Any review , retransmission, or further use of this e-mail by persons or entities other than the intended recipient is strictly prohibited.</p></td></tr>
<tr><td><p lang="en" style="font-size:x-small">Because of the nature of the Internet the sender is not in a position to ensure the integrity of this message, therefore the sender disclaims any liability whatsoever, in the event of this message having been intercepted and/or altered.</p></td></tr>
</table>
</font>
</PRE>

Search Discussions

  • Tom Lane at Feb 8, 2011 at 6:20 pm

    Cyril DE MURCIA writes:
    We use postgresql 7.3.2 under Linux Red Hat 9.0.
    We periodically dump and restore our database. I don't know if an error
    occured during a dump restore but our DB seems to be corrupted.
    Our base contains many pair of table with the same name.
    My goodness, that's a pretty obsolete system :-(. You do realize that
    7.3.x was up to 7.3.21 by the time it was obsoleted?

    My recollection is that this has been seen to happen when there were for
    some reason duplicate rows in pg_shadow --- pg_dump does something like
    "SELECT FROM pg_class JOIN pg_shadow ON relowner = usesysid", so it
    would get multiple copies of any table that joined to multiple pg_shadow
    entries. How you got into that state is harder to say, but if you can
    get rid of the duplicate entries then your dump would go back to a sane
    state.

    regards, tom lane
  • John R Pierce at Feb 8, 2011 at 6:56 pm

    On 02/08/11 10:20 AM, Tom Lane wrote:
    Cyril DE MURCIA<cyril.de-murcia@dcnsgroup.com> writes:
    We use postgresql 7.3.2 under Linux Red Hat 9.0.
    We periodically dump and restore our database. I don't know if an error
    occured during a dump restore but our DB seems to be corrupted.
    Our base contains many pair of table with the same name.
    My goodness, that's a pretty obsolete system :-(. You do realize that
    7.3.x was up to 7.3.21 by the time it was obsoleted?
    indeed. 7.3.2 was released in Feb 2003, 8 years ago, while 7.3.21 was
    5 years later, Jan 2008.

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
grouppgsql-bugs @
categoriespostgresql
postedFeb 8, '11 at 1:10p
activeFeb 8, '11 at 6:56p
posts3
users3
websitepostgresql.org
irc#postgresql

People

Translate

site design / logo © 2021 Grokbase