Re: Performance Optimisation - Identifying the correct DB - Mailing list pgsql-admin

From Ravi Krishna
Subject Re: Performance Optimisation - Identifying the correct DB
Date
Msg-id emcfc2fff3-8022-4d73-95be-f020f9a13171@ravis-macbook-pro.local
Whole thread Raw
In response to Performance Optimisation - Identifying the correct DB  (Renjith Gk <renjithgk@gmail.com>)
List pgsql-admin

What is the optimal execution time for Reading 200k records in Postgres. We had issues for reading records in cassandra which faced time out for ~200K records.

any ideal solution or recommendation towards Postgres.

Cassandra is highly optimized for key based readings only. 

Without knowing your application it is hard to predict how long will it take to read 200K records. 

Does the query to fetch 200K records use index. 
Does it fetch a small portion or a large portion of total rows. If later, then most likely PG will do table scan.  
How wide is the table.  
What is the timeout setting?

pgsql-admin by date:

Previous
From: Eshara Mondal
Date:
Subject: RE: Performance Optimisation - Identifying the correct DB
Next
From: Gary Orban
Date:
Subject: Postgres 9.3.10 on Centos6