pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Denis BUCHER <dbucherml@hsolutions.ch>
Cc: pgsql-sql@postgresql.org
Subject: Re: Problem with return type of function ??? (corrected)
Date: Thu, 22 Oct 2009 10:33:35 -0400
Message-ID: <29935.1256222015@sss.pgh.pa.us> (raw)
In-Reply-To: <4AE046E4.8010205@hsolutions.ch>
References: <4AE046E4.8010205@hsolutions.ch>

Denis BUCHER <dbucherml@hsolutions.ch> writes:
> I have a strange problem, because it worked in a fonction for a table,
> and now I created the same (?) function for another table and it doesn't
> work...

> The function is accepted but at runtime I get :

> ERREUR:  wrong record type supplied in RETURN NEXT
> CONTEXTE : PL/pgSQL function "find_sn_live" line 26 at return next

Does that table have any dropped columns?  If you don't remember
whether you ever dropped any columns, a quick look into pg_attribute
will tell you:
select attname from pg_attribute where attrelid = 'rma.serial_number'::regclass;

plpgsql isn't tremendously good with rowtypes that contain dropped
columns.  I believe this particular case is fixed in CVS HEAD, but the
patch was a bit invasive and won't get back-ported to existing releases.
The workaround is to drop and recreate the table without any dropped
columns.

			regards, tom lane



view thread (8+ messages)  latest in thread

Message-ID: <29935.1256222015@sss.pgh.pa.us>
Permalink:  ../29935.1256222015@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/29935.1256222015@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-sql@postgresql.org
  Cc: tgl@sss.pgh.pa.us, dbucherml@hsolutions.ch
  Subject: Re: Problem with return type of function ??? (corrected)
  In-Reply-To: <29935.1256222015@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