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

help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Rubén Crespo Flores <ruben.crespo1@gmail.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: Problem creating temporary tables . . .
Date: Thu, 20 Sep 2012 13:36:20 -0400
Message-ID: <26932.1348162580@sss.pgh.pa.us> (raw)
In-Reply-To: <CF523163-E84B-4D07-B98A-2ED5E0DD4E70@gmail.com>
References: <6F6C406D-518A-4E6F-ACE9-D234B6EB2418@gmail.com>
	<11992.1348090218@sss.pgh.pa.us>
	<CF523163-E84B-4D07-B98A-2ED5E0DD4E70@gmail.com>

=?iso-8859-1?Q?Rub=E9n_Crespo_Flores?= <ruben.crespo1@gmail.com> writes:
>>> ERROR: could not find tuple for attrdef 299038853
>>> SQL state: XX000
>>> Context: SQL statement "create temporary table tmp_tablatotlin15 (...

>> Hm ... that's a bit odd, but try reindexing pg_attrdef.

> I tried reindexing pg_attrdef and pg_attribute but the result was the same.

There's something awfully odd about that.  A look in the 9.0 sources
says that that specific error text only appears in RemoveAttrDefault
and getObjectDescription - and the latter is only used in error
messages.  It's not apparent why a CREATE TABLE operation would either
be dropping column defaults or issuing error messages that cite an
already-existing default.  Could you show a complete example of this
behavior?

BTW, please keep the mailing list cc'd, so that more people can help you.

			regards, tom lane




view thread (5+ messages)  latest in thread

Message-ID: <26932.1348162580@sss.pgh.pa.us>
Permalink:  ../26932.1348162580@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/26932.1348162580@sss.pgh.pa.us

 · 

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: tgl@sss.pgh.pa.us, ruben.crespo1@gmail.com
  Subject: Re: Problem creating temporary tables . . .
  In-Reply-To: <26932.1348162580@sss.pgh.pa.us>

* 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