Re: Detoasting optionally to make Explain-Analyze less misleading - Mailing list pgsql-hackers

From Matthias van de Meent
Subject Re: Detoasting optionally to make Explain-Analyze less misleading
Date
Msg-id CAEze2WhdmjbzVxgP8aW=0Dqynweh72QCdWRyxS24+1nmVopmrg@mail.gmail.com
Whole thread Raw
In response to Re: Detoasting optionally to make Explain-Analyze less misleading  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Detoasting optionally to make Explain-Analyze less misleading
List pgsql-hackers
On Wed, 3 Apr 2024 at 23:50, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> I've pushed this after a good deal of cosmetic polishing -- for
> example, I spent some effort on making serializeAnalyzeReceive
> look as much like printtup as possible, in hopes of making it
> easier to keep the two functions in sync in future.

Upthread at [0], Stepan mentioned that we should default to SERIALIZE
when ANALYZE is enabled. I suspect a patch in that direction would
primarily contain updates in the test plan outputs, but I've not yet
worked on that.

Does anyone else have a strong opinion for or against adding SERIALIZE
to the default set of explain features enabled with ANALYZE?

I'll add this to "Decisions to Recheck Mid-Beta"-section if nobody has
a clear objection.


Kind regards,

Matthias van de Meent
Neon (https://neon.tech)

[0] https://postgr.es/m/ea885631-21f1-425a-97ed-c4bfb8cf9c63%40gmx.de



pgsql-hackers by date:

Previous
From: Amit Kapila
Date:
Subject: Re: Is this a problem in GenericXLogFinish()?
Next
From: Tender Wang
Date:
Subject: Re: Can't find not null constraint, but \d+ shows that