Re: Deadlock with tsearch2 index ...

From: Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "Marc G(dot) Fournier" <scrappy(at)postgresql(dot)org>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Deadlock with tsearch2 index ...
Date: 2005-06-01 01:30:25
Message-ID: 429D0FB1.3000209@familyhealth.com.au
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> The real solution is to upgrade GIST to be concurrent. Oleg and Teodor
> have made some noises about that in the past, but nothing's been done
> about it that I've heard of.

This whole GiST concurrency think really needs to be looked at :( There
is so much cool stuff that can be done with it, and now that there are
som fantastic uses of it, such as tsearch2 and pg_trgm, people are
starting to run into these walls :(

WAL logging would also be nice, especially since Tom mentioned in the
manual that it was just a Small Matter Of Programming :D

Chris

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Christopher Kings-Lynne 2005-06-01 01:31:04 Re: Deadlock with tsearch2 index ...
Previous Message Hiroshi Saito 2005-06-01 01:29:10 Re: audit facilities?