From: Tom Lane <tgl@sss.pgh.pa.us>
To: maxim.boguk@gmail.com
cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17871: JIT during postgresql_fdw remote_estimates EXPLAIN
 have very negatively effect on planning time
In-reply-to: <17871-16521a70c16cb83c@postgresql.org>
References: <17871-16521a70c16cb83c@postgresql.org>
Comments: In-reply-to PG Bug reporting form <noreply@postgresql.org>
	message dated "Mon, 27 Mar 2023 08:04:59 -0000"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <3169905.1679928808.1@sss.pgh.pa.us>
Date: Mon, 27 Mar 2023 10:53:28 -0400
Message-ID: <3169906.1679928808@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/3169906.1679928808%40sss.pgh.pa.us>
Precedence: bulk

PG Bug reporting form <noreply@postgresql.org> writes:
> Checking what's going on the remote side leads to the following results:
> remote estimate explain calls from fdw with jit=on
> [EXPLAIN] LOG:  duration: 97.050 ms  statement: EXPLAIN SELECT topic_id,
> review_id, move_to_invitation_state_time, no_interview_reply_time,
> review_suggestion_chat_message_creation_time FROM
> public.interview_review_info_archive
> vs
> remote estimate explain calls from fdw with jit=off
> [EXPLAIN] LOG:  duration: 3.343 ms  statement: EXPLAIN SELECT topic_id,
> review_id, move_to_invitation_state_time, no_interview_reply_time,
> review_suggestion_chat_message_creation_time FROM
> public.interview_review_info_archive

Do you see the same discrepancy when you execute EXPLAIN manually
on the remote side?  If so, I wouldn't blame postgres_fdw for it.

I suppose interview_review_info_archive is a view not a plain table?
In either case, could we see the DDL definition for it?

			regards, tom lane