On Thu, May 4, 2017 at 8:36 AM, Scott Marlowe wrote:
> On Thu, May 4, 2017 at 8:10 AM, Junaid Malik wrote:
>> Hello Guys,
>>
>> We are facing problem related to performance of Postgres. Indexes are not
>> being utilized and Postgres is giving priority to seq scan. I read many
>> articles of Postg
On Thu, May 4, 2017 at 8:10 AM, Junaid Malik wrote:
> Hello Guys,
>
> We are facing problem related to performance of Postgres. Indexes are not
> being utilized and Postgres is giving priority to seq scan. I read many
> articles of Postgres performance and found that we need to set the
> randome_p
Hello Guys,
We are facing problem related to performance of Postgres. Indexes are not being
utilized and Postgres is giving priority to seq scan. I read many articles of
Postgres performance and found that we need to set the randome_page_cost value
same as seq_page_cost because we are using SSD
On 4 May 2017 at 22:52, wrote:
> I have a performance problem with my query. As a simplified example, I have
> a table called Book, which has three columns: id, released (timestamp) and
> author_id. I have a need to search for the latest books released by multiple
> authors, at a specific point i
On Thu, May 4, 2017 at 3:52 AM, wrote:
> Hi,
>
> I have a performance problem with my query. As a simplified example, I
> have a table called Book, which has three columns: id, released (timestamp)
> and author_id. I have a need to search for the latest books released by
> multiple authors, at a
Hi,
I have a performance problem with my query. As a simplified example, I have a
table called Book, which has three columns: id, released (timestamp) and
author_id. I have a need to search for the latest books released by multiple
authors, at a specific point in the history. This could be lates
