| From: | Karl Denninger <karl(at)denninger(dot)net> |
|---|---|
| To: | Richard Huxton <dev(at)archonet(dot)com> |
| Cc: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: 8.2.6 > 8.3 blows up |
| Date: | 2008-03-03 12:17:21 |
| Message-ID: | 47CBEC51.4050009@denninger.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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.
Karl Denninger (karl(at)denninger(dot)net)
http://www.denninger.net
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Richard Huxton | 2008-03-03 12:22:46 | Re: 8.2.6 > 8.3 blows up |
| Previous Message | Richard Huxton | 2008-03-03 12:04:16 | Re: how to auto GRANT custom ACL on a new table? |