Skip site navigation (1) Skip section navigation (2)

Re: 42804: structure of query does not match error where using RETURN QUERY

From: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
To: Michal Szymanski <mich20061(at)gmail(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: 42804: structure of query does not match error where using RETURN QUERY
Date: 2009-05-08 13:09:15
Message-ID: 162867790905080609y7b026385p5f2f2f584257e298@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-bugs
Hello

you have to do vacuum full  cerber.cerber_account

regards
Pavel Stehule

2009/5/8 Michal Szymanski <mich20061(at)gmail(dot)com>:
> Hi,
> We call DB procedure that select rows with given ID it works as simple
> SELECT but for future changes we implement as DB procedure (look below
> for DB listing). Recently we modified columns in table
> cerber.cerber_accoun and after this modification procedure does not
> work anymore and it returns
> 42804: structure of query does not match
> It is very strange because we return row of cerber_account in variable
> defined as row of cerber_account.
> We have tried to restart database but it does not help. Probably
> information about old table structure is somewhere cached.
>
> CREATE OR REPLACE FUNCTION cerber.cerber_account_select
> (i_cerber_account_id bigint)
>  RETURNS SETOF cerber.cerber_account AS
> $BODY$
> DECLARE
>        v_result cerber.cerber_account%ROWTYPE;
> BEGIN
>        RETURN QUERY SELECT * FROM cerber.cerber_account WHERE
> cerber_account_id=i_cerber_account_id;
>        RETURN;
> END;
> $BODY$
>  LANGUAGE 'plpgsql' VOLATILE
>  COST 100
>  ROWS 1000;
>
>
> --
> Sent via pgsql-bugs mailing list (pgsql-bugs(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-bugs
>

In response to

Responses

pgsql-bugs by date

Next:From: Dave PageDate: 2009-05-08 13:48:15
Subject: Re: BUG #4797: Uninstall : impossible to delete some files (base...)
Previous:From: Rafael MartinezDate: 2009-05-08 12:59:04
Subject: Re: BUG #4801: Performance failure: 600 MB written to each WAL log

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group