Bruce Momjian 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 ta
Tom Lane wrote:
> Michal Szymanski 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 abou
Michal Szymanski 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
> Exactly what modifications did you make?
We have added few new columns and we delete one column.
Michal Szymanski
http://blog.szymanskich.net
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
> you have to do vacuum full cerber.cerber_account
Yes I've made vacuum full - result was the same.
Regards
Michal Szymanski
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
We use Postgres 8.3.7 on Linux
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs