Re: moving some code out of explain.c - Mailing list pgsql-hackers

From Robert Haas
Subject Re: moving some code out of explain.c
Date
Msg-id CA+TgmoY+8MA1AkzLM7MiR7+yUDoT8b6r2OvVz_QF7j64C3WSHg@mail.gmail.com
Whole thread Raw
In response to Re: moving some code out of explain.c  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: moving some code out of explain.c
List pgsql-hackers
On Thu, Feb 27, 2025 at 4:12 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
> +1, but how about explain_dr.h too?  It doesn't seem though that
> we can avoid #include "executor/instrument.h" there, so it'd be
> a little asymmetrical.  But the executor inclusion doesn't seem
> nearly as much almost-circular.

OK, here is v2. One slightly unfortunate thing about this is that we
end up with a line that is over 80 characters:

extern DestReceiver *CreateExplainSerializeDestReceiver(struct
ExplainState *es);

Aside from perhaps shortening the function name, I don't see how to avoid that.

--
Robert Haas
EDB: http://www.enterprisedb.com

Attachment

pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: [PROPOSAL] : Disallow use of empty column name in (column_name '') in ALTER or CREATE of foreign table.
Next
From: Andy Alsup
Date:
Subject: Re: Update docs for UUID data type