| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Hannes Dorbath <light(at)theendofthetunnel(dot)de> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Segmentation fault with 8.3 FTS ISpell |
| Date: | 2008-01-15 17:10:39 |
| Message-ID: | 20080115171039.GH4473@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Hannes Dorbath wrote:
> Hannes Dorbath wrote:
>> Yes, I'll try to catch the row.
>
> I just slammed a BEFORE UPDATE FOR EACH ROW trigger with RAISE NOTICE on
> the table to catch the row ID where it fails.
>
> The row ID is never the same. Neither can I reproduce it when I use the
> last reported row ID.
>
> Is NOTICE logging / printing asynchron? Is there some sort of queuing that
> eats the ID where it really fails?
>
> Any ideas to track this down?
Turn off autovacuum and see if it makes any difference.
--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | blackwater dev | 2008-01-15 17:18:18 | bulk copy |
| Previous Message | Tom Lane | 2008-01-15 16:58:33 | Re: Prepared statement's planning |