RHEL 5.10 kernel 2.6.18
--
View this message in context:
http://postgresql.1045698.n5.nabble.com/Slow-query-wrong-index-used-maybe-tp5788979p5789206.html
Sent from the PostgreSQL - performance mailing list archive at Nabble.com.
--
Sent via pgsql-performance mailing list (pgsql-performance@p
On Mon, Jan 27, 2014, at 11:43, Gavin Flower wrote:
> On 28/01/14 08:10, bobJobS wrote:
> > My developers have had the same issue.
> >
> > Postgres 9.2.3 on Linux 5.6.
> >
> The latest Linux kernel is 3.13 (https://www.kernel.org), so I assume
> 5.6 is a distribution version.
>
> So which distr
On 28/01/14 08:10, bobJobS wrote:
My developers have had the same issue.
Postgres 9.2.3 on Linux 5.6.
The latest Linux kernel is 3.13 (https://www.kernel.org), so I assume
5.6 is a distribution version.
So which distribution of Linux are you using?
Cheers,
Gavin
--
Sent via pgsql-perform
My developers have had the same issue.
Postgres 9.2.3 on Linux 5.6.
The query planner estimates (for 27 table join SQL) that using the nestloop
is faster, when in fact it is not. A hashjoin returns results faster. We've
set enable_nestloop = false and have gotten good results. The problem is,
nes
Hello Stelian,
Have you tried to use func_table module?, I think it will help you to eliminate
all the joins.
Regards
On Monday, January 27, 2014 5:54 PM, Stelian Iancu wrote:
Hello,
I have Postrgres 9.3 running on a Linux machine with 32GB RAM. I have a
fairly large database (some table
On Mon, Jan 27, 2014, at 7:06, Tom Lane wrote:
> Stelian Iancu writes:
> > I have Postrgres 9.3 running on a Linux machine with 32GB RAM. I have a
> > fairly large database (some tables with approx. 1 mil. records) and I
> > have the following query:
> > [ 13-way join joined to a 3-way join ]
>
>
On Mon, Jan 27, 2014, at 9:20, salah jubeh wrote:
> Hello Stelian,
>
Hello,
> Have you tried to use func_table module?, I think it will help you to
> eliminate all the joins.
No, I haven't. I can have a look later, thanks.
>
> Regards
>
>
--
Sent via pgsql-performance mailing list (p
Stelian Iancu writes:
> I have Postrgres 9.3 running on a Linux machine with 32GB RAM. I have a
> fairly large database (some tables with approx. 1 mil. records) and I
> have the following query:
> [ 13-way join joined to a 3-way join ]
Think you'll need to raise join_collapse_limit and from_coll
Hello,
I have Postrgres 9.3 running on a Linux machine with 32GB RAM. I have a
fairly large database (some tables with approx. 1 mil. records) and I
have the following query:
SELECT * FROM (
SELECT DISTINCT c.ext_content_id AS type_1_id,
"substring"(c.ext_content_id::text, 1, 13) AS t
