On Tue, Oct 24, 2023 at 12:12:41AM +0000,
fujii.y...@df.mitsubishielectric.co.jp wrote:
> Hi Mr.Momjian.
>
> > Fujii-san, to get this patch closer to finished, can I modify this version
> > of the patch to improve some wording and post an
> > updated version you can use for future changes?
> Yes, I greatly appreciate your offer.
> I would very much appreciate your modifications.
I am almost done updating the patch, but I got stuck on how the feature
is supposed to work. This documentation sentence is where I got
confused:
<varlistentry>
<term><literal>check_partial_aggregate_support</literal>
(<type>boolean</type>)</term>
<listitem>
<para>
If this option is false, <filename>postgres_fdw</filename> assumes
that for each built-in aggregate function,
the partial aggregate function is defined on the remote server
without checking the remote server version.
If this option is true, during query planning,
<filename>postgres_fdw</filename> connects to the remote server
and checks if the remote server version is older than the local
server version.
If so,
<filename>postgres_fdw</filename>
--> assumes that for each built-in aggregate function, the partial
aggregate function is not defined
--> on the remote server unless the partial aggregate function and the
aggregate
--> function match.
Otherwise <filename>postgres_fdw</filename> assumes that for each
built-in aggregate function,
the partial aggregate function is defined on the remote server.
The default is <literal>false</literal>.
</para>
</listitem>
</varlistentry>
What does that marked sentence mean? What is match? Are one or both of
these remote? It sounds like you are checking the local aggregate
against the remote partial aggregate, but I don't see any code that does
this in the patch.
--
Bruce Momjian <br...@momjian.us> https://momjian.us
EDB https://enterprisedb.com
Only you can decide what is important to you.
