I was suspecting that it was incompatibility that hadn't been documented
correctly, just wanted to make sure that this was the case.
It probably should go into the release notes too since it is bound to affect
others....
Thankfully
Marcel Asio
Network & System Administrator
Redbet Technology
Mobile: +46 (0)709 13 04 01
Work: +46 (0)8 12 09 99 41
marcel.asio@redbet.com
This e-mail may contain confidential and/or privileged information. If you
are not the intended recipient (or have received this e-mail in error)
please notify the sender immediately and destroy this e-mail. Any
unauthorised copying, disclosure or distribution of the material in this
e-mail is strictly forbidden.
On 29 June 2010 19:38, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Marcel Asio <marcel.asio@redbet.com> writes:
> > Yes I managed to figured that out, but when was this changed?
>
> > It was working in 8.4 but not 9.0 and I could not find anything about
> this in the release notes.
>
> The 9.0 release notes are not really up to snuff yet :-(. The only
> thing in the notes about it is "Allow PL/pgSQL to handle row types with
> dropped columns" which is a rather inadequate description of the
> consequences of that patch. We're probably going to need to call it out
> as an incompatibility.
>
> regards, tom lane
>
