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 Ex
>> What if we do something like a new EXPLAIN option which returns all
>> the rows
>> back to the client, and then writes out the plan to some local
>> memory.
> That's another idea, but I am starting to think returning two result
> sets from EXPLAIN ANALYZE would be generally useful.
I did not t
Jeff Davis writes:
> Ideally, we'd have EXPLAIN ANALYZE return two result sets, kind of like
> how a query with a semicolon returns two result sets. That changes the
> expected message flow for EXPLAIN ANALYZE, though, so we'd need a new
> option so we are sure the client is expecting it (is this
On Wed, 2025-02-26 at 13:13 -0600, Sami Imseih wrote:
> 1/ The use of NOTICE to propagate the explain plan.
> I see the message content is checked, but this does not look robust
> and could lead to
> some strange results if another ExecutorRun hook emits a similar
> notice message.
Fundamentally,
Hi,
Thanks for working on this patch!
I looked at the patch from and I have several comments. There are
some others, but wanted to start with the most important I found, in order
of importance.
1/ The use of NOTICE to propagate the explain plan.
I see the message content is checked, but this doe
On Mon, Nov 25, 2024 at 10:23 PM Anton Shmigirilov <
a.shmigiri...@postgrespro.ru> wrote:
>
> > Hi Hackers,
> >
> > I am working on a feature in postgres_fdw extension to show plans used
> by remote postgresql servers in the output of the EXPLAIN command.
> > I think this will help end users under
> Hi Hackers,
>
> I am working on a feature in postgres_fdw extension to show plans used by
> remote postgresql servers in the output of the EXPLAIN command.
> I think this will help end users understand query execution plans used by
> remote servers. Sample output for table people where peopl
On Tue, Nov 12, 2024 at 4:16 PM Ashutosh Bapat
wrote:
> On Mon, Nov 11, 2024 at 9:12 PM dinesh salve
> wrote:
> >
> >
> > Hi Hackers,
> >
> > I am working on a feature in postgres_fdw extension to show plans used
> by remote postgresql servers in the output of the EXPLAIN command.
> > I think th
On Mon, Nov 11, 2024 at 9:12 PM dinesh salve wrote:
>
>
> Hi Hackers,
>
> I am working on a feature in postgres_fdw extension to show plans used by
> remote postgresql servers in the output of the EXPLAIN command.
> I think this will help end users understand query execution plans used by
> remo
dinesh salve writes:
Hi,
>
> I am working on a feature in postgres_fdw extension to show plans used
> by remote postgresql servers in the output of the EXPLAIN command.
>
> I think this will help end users understand query execution plans used
> by remote servers. Sample output for table people
Hi Hackers,
I am working on a feature in postgres_fdw extension to show plans used by
remote postgresql servers in the output of the EXPLAIN command.
I think this will help end users understand query execution plans used by
remote servers. Sample output for table people where people_1 is local
par
11 matches
Mail list logo
