On Wed, Dec 16, 2015 at 11:41 PM, Tom Lane wrote:
> Robert Haas writes:
> > I like option #2. I don't really have a strong reason for that, but
> > it feels intuitive to me that we err on the side of using remote
> > estimates when in doubt.
>
> If we believe that, why isn't the default value o
On Wed, Dec 16, 2015 at 1:11 PM, Tom Lane wrote:
> Robert Haas writes:
>> I like option #2. I don't really have a strong reason for that, but
>> it feels intuitive to me that we err on the side of using remote
>> estimates when in doubt.
>
> If we believe that, why isn't the default value of use
Robert Haas writes:
> I like option #2. I don't really have a strong reason for that, but
> it feels intuitive to me that we err on the side of using remote
> estimates when in doubt.
If we believe that, why isn't the default value of use_remote_estimate true?
(Maybe it should be.)
Another opti
On Fri, Dec 11, 2015 at 4:44 AM, Ashutosh Bapat
wrote:
> Hi All,
> postgres_fdw documentation says following about use_remote_estimate
> (http://www.postgresql.org/docs/devel/static/postgres-fdw.html)
> --
> use_remote_estimate
> This option, which can be specified for a foreign table or a foreign
Hi All,
postgres_fdw documentation says following about use_remote_estimate (
http://www.postgresql.org/docs/devel/static/postgres-fdw.html)
--
use_remote_estimate
This option, which can be specified for a foreign table or a foreign
server, controls whether postgres_fdw issues remote EXPLAIN comman
