pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Matthias van de Meent <boekewurm+postgres@gmail.com>
Cc: stepan rutz <stepan.rutz@gmx.de>
Cc: Tomas Vondra <tomas.vondra@enterprisedb.com>
Cc: pgsql-hackers@postgresql.org
Subject: Re: Detoasting optionally to make Explain-Analyze less misleading
Date: Wed, 10 Apr 2024 09:57:35 -0400
Message-ID: <4017527.1712757455@sss.pgh.pa.us> (raw)
In-Reply-To: <CAEze2WhdmjbzVxgP8aW=0Dqynweh72QCdWRyxS24+1nmVopmrg@mail.gmail.com>
References: <ca0adb0e-fa4e-c37e-1cd7-91170b18cae1@gmx.de>
	<CAEze2WhXYCJ8=ZBTbRTp9rGbvju9LK6UO7hodECKWgU-_a==aw@mail.gmail.com>
	<2802772.1694532399@sss.pgh.pa.us>
	<ce7edfd9-dcc5-2203-5ce5-051ca229b75a@gmx.de>
	<03f952d6-b773-be93-e5d5-8f9ea9c2d461@gmx.de>
	<7b7d46b1-d6f7-eb10-55c9-aa45fce57781@enterprisedb.com>
	<9126b7da-204b-4701-8e2b-37fb824a0cf4@gmx.de>
	<78507aa1-f850-50cd-458a-3986d973d092@enterprisedb.com>
	<CAEze2WjrZST8YEhV_oYXzC8y=P5aRGCMe_QpwhdK1PmNpjCeWQ@mail.gmail.com>
	<886b209f-8736-9cf2-ab9c-89870dea7bd8@enterprisedb.com>
	<CAEze2Wg8UMUuT9sHpWGCeBzm-nHTbQcnPsSob4ynAPXjiD-G=Q@mail.gmail.com>
	<14746b40-16a8-b53e-18a6-f2872e696e34@enterprisedb.com>
	<CAEze2WiLjoAYTcaaSR=pMK1SaZHMDh4Z7yeDeDrk3B7zNVA4gA@mail.gmail.com>
	<ea885631-21f1-425a-97ed-c4bfb8cf9c63@gmx.de>
	<CAEze2Wj=w+qDtPqM7qt-ZRXbG7vmvONa-ocfQZ1inGuE58zrRg@mail.gmail.com>
	<1642956.1712072848@sss.pgh.pa.us>
	<CAEze2WhopAFRS4xdNtma6XtYCRqydPWAg83jx8HZTowpeXzOyg@mail.gmail.com>
	<384054.1712181051@sss.pgh.pa.us>
	<CAEz! e2WhdmjbzVxgP8aW=0Dqynweh72QCdWRyxS24+1nmVopmrg@mail.gmail.com>

Matthias van de Meent <boekewurm+postgres@gmail.com> writes:
> 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 am 100% dead set against that, because it would silently render
EXPLAIN outputs from different versions quite non-comparable.

			regards, tom lane





view thread (28+ messages)  latest in thread

Message-ID: <4017527.1712757455@sss.pgh.pa.us>
Permalink:  ../4017527.1712757455@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/4017527.1712757455@sss.pgh.pa.us

 · 

reply
Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: tgl@sss.pgh.pa.us, boekewurm+postgres@gmail.com, stepan.rutz@gmx.de, tomas.vondra@enterprisedb.com
  Subject: Re: Detoasting optionally to make Explain-Analyze less misleading
  In-Reply-To: <4017527.1712757455@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox