Re: Join Bad Performance on different data types - Mailing list pgsql-general

From Sameer Kumar
Subject Re: Join Bad Performance on different data types
Date
Msg-id CADp-Sm4kqYg-hrZPLgTTYOzLes83i6NnZH3TGvW=nmAcLbQs2A@mail.gmail.com
Whole thread Raw
In response to Re: Join Bad Performance on different data types  (Adarsh Sharma <eddy.adarsh@gmail.com>)
List pgsql-general

On Tue, Mar 4, 2014 at 4:19 PM, Adarsh Sharma <eddy.adarsh@gmail.com> wrote:
Is dere any way i can rewrite the query so that i need not to set seqscan-off,  because i dont want to embed one more line in application code and also dont want to change global setting in postgresql.conf to disable seqscan.

You can use a specific user for this query and set parameter's value at user level.

But if you don't have any way of doing that then you pretty much have to "embed one more line in application code" [though I have never understood why application teams do not want to do that]. It should be fine, unless you are developing a product which can be used with someother RDBMS and hence you don't want to introduce a PostgreSQL specific line in code.



Best Regards,

Sameer Kumar | Database Consultant

ASHNIK PTE. LTD.

101 Cecil Street, #11-11 Tong Eng Building, Singapore 069533

M: +65 8110 0350  T: +65 6438 3504 | www.ashnik.com

icons

 

Email patch

 

This email may contain confidential, privileged or copyright material and is solely for the use of the intended recipient(s).

Attachment

pgsql-general by date:

Previous
From: Adarsh Sharma
Date:
Subject: Re: Join Bad Performance on different data types
Next
From: leo
Date:
Subject: Re: How to recovery failed master after failover