Re: 8.2.6 > 8.3 blows up - Mailing list pgsql-general

From Karl Denninger
Subject Re: 8.2.6 > 8.3 blows up
Date
Msg-id 47CC0718.8010409@denninger.net
Whole thread Raw
In response to Re: 8.2.6 > 8.3 blows up  (Richard Huxton <dev@archonet.com>)
Responses Re: 8.2.6 > 8.3 blows up  (Richard Huxton <dev@archonet.com>)
List pgsql-general
I can reproduce this as I have the dump from "before conversion" and can
load it on a different box and "make it happen" a second time.

Would you like it on the list or privately?

Karl Denninger (karl@denninger.net)
http://www.denninger.net




Richard Huxton wrote:
> Karl Denninger wrote:
>> Richard Huxton wrote:
>>> Karl Denninger wrote:
>>>>
>>>> The problem is that I was holding the ts_vector in a column in the
>>>> table with a GIST index on that column.  This fails horribly under
>>>> 8.3; it appears to be ok on the reload but as there is a trigger on
>>>> updates any update or insert fails immediately with a data mistype
>>>> complaint.
>>>
>>> Are you sure you've not got an old definition of tsvector/tsquery or
>>> some such? I've got a tsvector column in a table, updated from a
>>> trigger with a gist index and it's fine. That's all created for 8.3
>>> though, not dumped/restored from 8.2
>>>
>> Quite sure; I just did it "by the book".  The simple fix was to get
>> rid of that and re-write the queries, which I've now done.
>
> Do you have a record of what the type error was, and what triggered
> it? If this is reproducable we'll need to change the docs.
>



pgsql-general by date:

Previous
From: Steve Clark
Date:
Subject: Re: ecpg problem
Next
From: Richard Huxton
Date:
Subject: Re: 8.2.6 > 8.3 blows up