Hello Andres,
with enable_bitmapscan=off; could you do :
explain ( analyze , buffers ) select * from entity2document2 where
name='ranitidine' ;
I think it's interesting to understand how much it's clustered the table
entity2document2.
infact the query extract 13512 rows
On Tue, Mar 11, 2014 at 3:30 AM, acanada wrote:
> Hello Evgeniy!
>
> I can move the database to another server...
> This is the cat of /proc/cpuinfo. Does it have enough power or should I go
> for a better one??
>
> (It has 32 processors like this one):
>
> cat /proc/cpuinfo
> processor : 0
Hello Evgeniy!
I can move the database to another server...
This is the cat of /proc/cpuinfo. Does it have enough power or should I go for
a better one??
(It has 32 processors like this one):
cat /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model
On 07 Mar 2014, at 13:18, acanada wrote:
> The table entity2document2 has 30GB. In consecutive runs it gets much
> better... 30ms apron.
So you just benchmarking your hard drives with random iops.
You need more ram and faster disks.
--
Sent via pgsql-performance mailing list (pgsql-performa
On Mon, Mar 10, 2014 at 4:46 AM, Jeff Janes wrote:
>
> On Fri, Mar 7, 2014 at 6:46 PM, Mohan Krishnan wrote:
>>
>> Hello folks,
>>
>> I have a table of about 700k rows in Postgres 9.3.3, which has the
>> following structure:
>>
>> Columns:
>> content_body - text
>> publish_date - timestamp wi
