Re: enabling nestedloop and disabling hashjon

sorry for the inconvenience if caused to anyone, but as David G johnston
said, I was trying to change how the postgresql works and was not able to
figure out how it should be done. I will make sure it will be clear from
the next time. Thank you very much.

@Tom lane Sir, I forgot to remove the # comment marker in the file's
entry, Thank you.
ᐧ

On Fri, Feb 13, 2015 at 2:50 AM, David G Johnston <
david(dot)g(dot)johnston(at)gmail(dot)com> wrote:

> Jim Nasby-5 wrote
> > On 2/10/15 9:29 AM, Tom Lane wrote:
> >> Ravi Kiran &lt;
>
> > ravi.kolanpaka@
>
> > &gt; writes:
> >>> yes sir, I did try the pg_ctl reload command, but its still using the
> >>> hash
> >>> join algorithm and not the nested loop algorithm. I even restarted the
> >>> server, even then its still using the hash join algorithm
> >>
> >> Does "show enable_hashjoin" say it's off? If not, I think you must've
> >> fat-fingered the postgresql.conf change somehow.
> >
> > For future reference, posts like this belong on pgsql-performance.
>
>
> > but postgres is still using the hash join algorithm even after modifying
> > the postgresql code
>
> To be fair given the original post, and some other recent posts by the same
> author, the question is not "why is my query performing slowly" but rather
> "I'm trying to change how PostgreSQL works and cannot figure out how to
> properly enable and disable algorithms". -hackers seems like the proper
> forum though the OP could give more context as to his overarching goals to
> make that more clear to readers.
>
> David J.
>
>
>
>
> --
> View this message in context:
> http://postgresql.nabble.com/enabling-nestedloop-and-disabling-hashjon-tp5837275p5837728.html
> Sent from the PostgreSQL - hackers mailing list archive at Nabble.com.
>
>
> --
> Sent via pgsql-hackers mailing list (pgsql-hackers(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-hackers
>