On 12/2/15 18:29, Tom Lane wrote:
> Ravi Kiran writes:
>> I am sorry for the late reply, when I disabled the hash join command
>> "enable_hashjoin=off" in the postgresql.conf file, it was not working. But
>> I when I used the command "set enable_hashjoin=off" command in the back
>> end. It worked
On 2/12/15 3:34 PM, Ravi Kiran wrote:
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.
A
On 2/12/15 3:20 PM, David G Johnston wrote:
>>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 ev
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 #
Ravi Kiran writes:
> I am sorry for the late reply, when I disabled the hash join command
> "enable_hashjoin=off" in the postgresql.conf file, it was not working. But
> I when I used the command "set enable_hashjoin=off" command in the back
> end. It worked.
> I am not able to understand why it
Jim Nasby-5 wrote
> On 2/10/15 9:29 AM, Tom Lane wrote:
>> Ravi Kiran <
> ravi.kolanpaka@
> > 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
I am sorry for the late reply, when I disabled the hash join command
"enable_hashjoin=off" in the postgresql.conf file, it was not working. But
I when I used the command "set enable_hashjoin=off" command in the back
end. It worked.
I am not able to understand why it did not get disabled when I ch
On 2/10/15 9:29 AM, Tom Lane wrote:
Ravi Kiran 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
Ravi Kiran 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'
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
Thanks
ᐧ
On Tue, Feb 10, 2015 at 5:28 AM, Tom Lane wrote:
> Ravi Kiran writes:
> > I tried
Ravi Kiran writes:
> I tried modifying the postgresql.conf file where I set the value
> enable_hashjoin=off and also enable_mergejoin=off, so that I could force
> postgres to use nested loop.
> but postgres is still using the hash join algorithm even after modifying
> the postgresql code.
Did you
Hi,
I want to disable the hashjoin algorithm used by postgres by default, and
enable the nested loop join algorithm, can some one tell me how to do that.
I tried modifying the postgresql.conf file where I set the value
enable_hashjoin=off and also enable_mergejoin=off, so that I could force
post
12 matches
Mail list logo
