2009/11/15 Oleg Bartunov :
> Yes, as stated original author use polish ispell dictionary.
> Ispell dictionary is slow to load first time. In real life it should be no
> problem.
>
it is a problem. People who needs fast access uses english without
czech. It drop some features, but it is significaly
Yes, as stated original author use polish ispell dictionary.
Ispell dictionary is slow to load first time. In real life it should
be no problem.
Oleg
On Sat, 14 Nov 2009, Pavel Stehule wrote:
2009/11/14 Tom Lane :
> Kenneth Marshall writes:
>> On Sat, Nov 14, 2009 at 12:25:05PM +0100, Wojcie
* I could buy two X25-E drives and have 32GB disk space, and some
redundancy. This would cost about $1600, not counting the RAID
controller. It is on the edge.
This was the solution I went with (4 drives in a raid 10 actually).
Not a cheap solution, but the performance is amazing.
Robert Haas wrote:
2009/11/14 Laszlo Nagy :
32GB is for one table only. This server runs other applications, and you
need to leave space for sort memory, shared buffers etc. Buying 128GB memory
would solve the problem, maybe... but it is too expensive. And it is not
safe. Power out -> data lo
Matthew Wakeling writes:
> [ discussion about applying materialize to a mergejoin's inner indexscan ]
I have finally gotten round to doing something about this, and applied
the attached patch to CVS HEAD. Could you test it on your problem case
to see what happens? If it's not convenient to load
On Sat, Nov 14, 2009 at 8:47 AM, Heikki Linnakangas
wrote:
> Merlin Moncure wrote:
>> On Sat, Nov 14, 2009 at 6:17 AM, Heikki Linnakangas
>> wrote:
lots of ram doesn't help you if:
*) your database gets written to a lot and you have high performance
requirements
>>> When all the (h
2009/11/14 Laszlo Nagy :
> 32GB is for one table only. This server runs other applications, and you
> need to leave space for sort memory, shared buffers etc. Buying 128GB memory
> would solve the problem, maybe... but it is too expensive. And it is not
> safe. Power out -> data loss.
Huh?
...Rob
Heikki Linnakangas wrote:
Laszlo Nagy wrote:
* I need at least 32GB disk space. So DRAM based SSD is not a real
option. I would have to buy 8x4GB memory, costs a fortune. And
then it would still not have redundancy.
At 32GB database size, I'd seriously consider just buying
2009/11/14 Tom Lane :
> Kenneth Marshall writes:
>> On Sat, Nov 14, 2009 at 12:25:05PM +0100, Wojciech Knapik wrote:
>>> I just finished implementing a "search engine" for my site and found
>>> ts_headline extremely slow when used with a Polish tsearch configuration,
>>> while fast with English.
>
Kenneth Marshall writes:
> On Sat, Nov 14, 2009 at 12:25:05PM +0100, Wojciech Knapik wrote:
>> I just finished implementing a "search engine" for my site and found
>> ts_headline extremely slow when used with a Polish tsearch configuration,
>> while fast with English.
> The documentation for ts
On Sat, Nov 14, 2009 at 12:25:05PM +0100, Wojciech Knapik wrote:
>
> Hello
>
> I just finished implementing a "search engine" for my site and found
> ts_headline extremely slow when used with a Polish tsearch configuration,
> while fast with English. All of it boils down to a simple testcase, bu
Merlin Moncure wrote:
> On Sat, Nov 14, 2009 at 6:17 AM, Heikki Linnakangas
> wrote:
>>> lots of ram doesn't help you if:
>>> *) your database gets written to a lot and you have high performance
>>> requirements
>> When all the (hot) data is cached, all writes are sequential writes to
>> the WAL,
On Sat, Nov 14, 2009 at 6:17 AM, Heikki Linnakangas
wrote:
>> lots of ram doesn't help you if:
>> *) your database gets written to a lot and you have high performance
>> requirements
>
> When all the (hot) data is cached, all writes are sequential writes to
> the WAL, with the occasional flushing
Hello
I just finished implementing a "search engine" for my site and found
ts_headline extremely slow when used with a Polish tsearch
configuration, while fast with English. All of it boils down to a simple
testcase, but first some background.
I tested on 8.3.1 on G5/OSX 10.5.8 and Xeon/G
Merlin Moncure wrote:
> 2009/11/13 Heikki Linnakangas :
>> Laszlo Nagy wrote:
>>>* I need at least 32GB disk space. So DRAM based SSD is not a real
>>> option. I would have to buy 8x4GB memory, costs a fortune. And
>>> then it would still not have redundancy.
>> At 32GB database size,
Lists wrote:
Laszlo Nagy wrote:
Hello,
I'm about to buy SSD drive(s) for a database. For decision making, I
used this tech report:
http://techreport.com/articles.x/16255/9
http://techreport.com/articles.x/16255/10
Here are my concerns:
* I need at least 32GB disk space. So DRAM based SS
Laszlo Nagy wrote:
Hello,
I'm about to buy SSD drive(s) for a database. For decision making, I
used this tech report:
http://techreport.com/articles.x/16255/9
http://techreport.com/articles.x/16255/10
Here are my concerns:
* I need at least 32GB disk space. So DRAM based SSD is not a rea
17 matches
Mail list logo
