From: | Ravi Kiran <ravi(dot)kolanpaka(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: enabling nestedloop and disabling hashjon |
Date: | 2015-02-10 08:54:10 |
Message-ID: | CAOh57xGjc07j_77vT2yqQkb_9BSiRsHsTYxNzgrN68rL9VqDTQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
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 <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Ravi Kiran <ravi(dot)kolanpaka(at)gmail(dot)com> 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 remember "pg_ctl reload"? enable_hashjoin=off will most certainly
> work if it's active.
>
> regards, tom lane
>
From | Date | Subject | |
---|---|---|---|
Next Message | Heikki Linnakangas | 2015-02-10 09:07:49 | Re: What exactly is our CRC algorithm? |
Previous Message | Michael Paquier | 2015-02-10 08:31:40 | Re: Table-level log_autovacuum_min_duration |