From: | Postgres User <postgres(dot)developer(at)gmail(dot)com> |
---|---|
To: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | How to check status of bug (42804: structure of query does not match error where using RETURN QUERY) ? |
Date: | 2009-12-07 00:28:50 |
Message-ID: | b88c3460912061628xae222f2oa184ac1d378f2150@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hi,
I've encountered a serious Postgres bug which apparently has a fix
that hasn't been released in a patch. How or where can I look up its
status?
This is a serious bug- it basically renders RETURN QUERY useless in
any environment where you don't have the option of dropping and
re-creating a table, so I'm surprised to see that it's been
outstanding for this long.
42804: structure of query does not match error where using RETURN QUERY
Tom Lane wrote:
> Michal Szymanski <mich20061(at)(dot)(dot)(dot)> writes:
> >> Exactly what modifications did you make?
>
> > We have added few new columns and we delete one column.
>
> [ experiments... ] Hmm, looks like RETURN QUERY isn't too bright about
> dropped columns in the function result type. I'm not too sure about how
> hard this is to fix, but in the meantime you will need to dump and
> recreate/reload that particular table in order to get it to work.
Is this a TODO?
--
Bruce Momjian <bruce(at)(dot)(dot)(dot)> http://momjian.us
EnterpriseDB http://enterprisedb.com
--
Sent via pgsql-bugs mailing list (pgsql-bugs(at)(dot)(dot)(dot))
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
Re: Re: 42804: structure of query does not match error where using
RETURN QUERY
by Tom Lane-2 Jun 02, 2009; 07:47am :: Rate this Message: - Use
ratings to moderate (?)
Reply | Reply to Author | Print | View Threaded | Show Only this Message
Bruce Momjian <bruce(at)(dot)(dot)(dot)> writes:
> Tom Lane wrote:
>> [ experiments... ] Hmm, looks like RETURN QUERY isn't too bright about
>> dropped columns in the function result type. I'm not too sure about how
>> hard this is to fix, but in the meantime you will need to dump and
>> recreate/reload that particular table in order to get it to work.
> Is this a TODO?
It's already there.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | A B | 2009-12-07 07:00:49 | Help! xlog flush request is not satisfied |
Previous Message | Jean-Yves F. Barbier | 2009-12-06 22:21:59 | Re: What packages I need to install to get Postgres working |