Odd Invalid type name error in postgresql 9.1

From: Jim Wilson <jimw(at)kelcomaine(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: Odd Invalid type name error in postgresql 9.1
Date: 2012-09-26 19:55:56
Message-ID: CALM6-3ewZOr8f+xMpq2ShSkhzWnoRWsAfRdyN46F9GVn2Jm4KQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Hi,

After upgrading from 8.3 I found an unusual error related to a plpgsql function.

The database includes a table named "detail".

The procedure/function in question includes a declaration of detail%rowtype.

Loading the server from a dump-all at the time of the upgrade went
fine and the function was loaded along with all the other database
objects. I noticed later on that at runtime (e.g. calling the
function) I was receiving an "invalid type name" error on the
declaration using "detail%rowtype".

This seemed odd. I couldn't find any record of "detail" being a
reserved word, and the usual sql queries using the table perform
without a hitch. But when I changed the declaration in the function to
have quotes around the table name (e.g. "detail"%rowtype) the error
went away.

Any ideas on this? My biggest concern is if there is a structural
problem in the database that might result in a crash later, I'd like
to get it fixed now.

Thanks in advance,

Jim Wilson

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Shaun Thomas 2012-09-26 20:03:03 Re: Inaccurate Explain Cost
Previous Message Adrian Klaver 2012-09-26 19:26:28 Re: trigger and plpgsq help needed