| From: | Tomas Vondra <tomas(dot)vondra(at)enterprisedb(dot)com> |
|---|---|
| To: | stepan rutz <stepan(dot)rutz(at)gmx(dot)de>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Matthias van de Meent <boekewurm+postgres(at)gmail(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Detoasting optionally to make Explain-Analyze less misleading |
| Date: | 2023-11-02 17:49:34 |
| Message-ID: | 7b7d46b1-d6f7-eb10-55c9-aa45fce57781@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
On 9/15/23 22:09, stepan rutz wrote:
> Hi,
>
> please see a revised version yesterday's mail. The patch attached now
> provides the following:
>
> EXPLAIN(ANALYZE,SERIALIZE)
>
> and
>
> EXPLAIN(ANALYZE,SERIALIZEBINARY)
>
I haven't looked at the patch in detail yet, but this option name looks
a bit strange/inconsistent. Either it should be SERIALIZE_BINARY (to
match other multi-word options), or maybe there should be just SERIALIZE
with a parameter to determine text/binary (like FORMAT, for example).
So we'd do either
EXPLAIN (SERIALIZE)
EXPLAIN (SERIALIZE TEXT)
to get serialization to text (which I guess 99% of people will do), or
EXPLAIN (SERIALIZE BINARY)
to get binary.
regards
--
Tomas Vondra
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Phil Eaton | 2023-11-02 17:58:42 | Add minimal C example and SQL registration example for custom table access methods. |
| Previous Message | Tomas Vondra | 2023-11-02 17:37:32 | Re: Postgres picks suboptimal index after building of an extended statistics |