On Mon, Nov 21, 2005 at 16:50:00 +0300,
Oleg Bartunov <oleg@sai.msu.su> wrote:
> On Mon, 21 Nov 2005, Hannes Dorbath wrote:
>
> >I'm playing a bit with it ATM. Indexing one Gigabyte of plain text worked
> >well, with 10 GB I yet have some performance problems. I read the TSearch
> >Tuning Guide and will start optimizing some things, but is it a realistic
> >goal to index ~90GB plain text and get sub-second response times on
> >hardware that ~4000 EUR can buy?
>
> What's ATM ? As for the sub-second response times it'd very depend on
> your data and queries. It'd be certainly possible with our tsearch daemon
> which we postponed, because we inclined to implement inverted indices first
> and then build fts index on top of inverted index. But this is long-term
> plan.
I believe in this context, 'ATM' is an ancronym for 'at the moment' which
has little impact on the meaning of the paragraph.
---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
