| From: | dinesh salve <cooltodinesh(at)gmail(dot)com> |
|---|---|
| To: | Sami Imseih <samimseih(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org, Jeff Davis <pgsql(at)j-davis(dot)com> |
| Subject: | Re: explain plans for foreign servers |
| Date: | 2025-11-18 03:25:39 |
| Message-ID: | CAP+B4TDxE3gbrixL9qR9F+CK_N_N0-HmXSL55QXVZNAorRHSHQ@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi Sami,
Thanks for the feedback. I have refactored the commit on the latest version
of PG and added a few more tests. To simplify the roll out of this feature,
I decided to work on analyze=false use case first. Please find the attached
patch for the same.
Regards,
Dinesh
On Thu, Mar 6, 2025 at 4:54 AM Jeff Davis <pgsql(at)j-davis(dot)com> wrote:
> On Wed, 2025-03-05 at 14:12 -0500, Tom Lane wrote:
> > I'm afraid not. That pretty fundamentally breaks the wire protocol,
> > I think.
>
> The extended protocol docs say: "The possible responses to Execute are
> the same as those described above for queries issued via simple query
> protocol, except that Execute doesn't cause ReadyForQuery or
> RowDescription to be issued."
>
> Each result set needs a RowDescription, so I think you're right that it
> breaks the extended protocol. I missed that the first time.
>
> Regards,
> Jeff Davis
>
>
--
Regards,
Dinesh Salve
Cell:- 91 8125898845
| Attachment | Content-Type | Size |
|---|---|---|
| 0001-This-change-adds-capability-to-fetch-explain-plans-f.patch | application/octet-stream | 59.1 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Kim | 2025-11-18 03:32:01 | Re: Proposal for enabling auto-vectorization for checksum calculations |
| Previous Message | 高增琦 | 2025-11-18 02:54:31 | Re: Compile error on the aarch64 platform: Missing asm/hwcap.h |