Re: [PERFORM] Yet another abort-early plan disaster on 9.3

2014-12-04 Thread Simon Riggs
On 30 September 2014 at 05:53, Simon Riggs wrote: > On 29 September 2014 16:00, Merlin Moncure wrote: >> On Fri, Sep 26, 2014 at 3:06 AM, Simon Riggs wrote: >>> The problem, as I see it, is different. We assume that if there are >>> 100 distinct values and you use LIMIT 1 that you would only nee

Re: [PERFORM] Query doesn't use index on hstore column

2014-12-04 Thread Tom Lane
Michael Barker writes: > I'm currently experimenting with hstore on Posgtres 9.4rc1. I've created a > table with an hstore column, with and index on that column (tried both gin > and btree indexes) and the explain plan says that the index is never used > for the lookup and falls to a sequential s

Re: [PERFORM] Query doesn't use index on hstore column

2014-12-04 Thread k...@rice.edu
On Fri, Dec 05, 2014 at 09:42:20AM +1300, Michael Barker wrote: > 1) Created table with hstore column and btree index. > > barkerm=# \d audit >Table "public.audit" > Column |Type | > Modifiers > ---+--

[PERFORM] Query doesn't use index on hstore column

2014-12-04 Thread Michael Barker
Hi, Apologies if this is the wrong list for this time of query (first time posting). I'm currently experimenting with hstore on Posgtres 9.4rc1. I've created a table with an hstore column, with and index on that column (tried both gin and btree indexes) and the explain plan says that the index i

Re: [PERFORM] issue in postgresql 9.1.3 in using arrow key in Solaris platform

2014-12-04 Thread Josh Berkus
On 11/26/2014 02:16 AM, M Tarkeshwar Rao wrote: > Hi all, > > > > We are facing following issue in postgresql 9.1.3 in using arrow key in > Solaris platform. > > *Can you please help us to resolve it or any new release has fix for > this or any workaround for this?* Mr. Rao: 1) Please do not