Re: small fix for pg_overexplain docs

From: Nathan Bossart <nathandbossart(at)gmail(dot)com>
To: Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com>
Cc: Robert Treat <rob(at)xzilla(dot)net>, "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: small fix for pg_overexplain docs
Date: 2025-07-16 21:22:56
Message-ID: aHgYMP_1l15Kiqmq@nathan
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Jul 16, 2025 at 07:45:05PM +0100, Dean Rasheed wrote:
> Maybe. It's kind-of annoying that all the modules that aren't
> extensions use different text. Maybe there are genuine differences --
> I didn't look too closely. It would be nice if we just had one
> standard description that they all could refer to, but if that's
> possible, it's a much bigger patch than you probably want to worry
> about here, so I'm happy to go with your text above.

Okay, here is a new version of the patch.

--
nathan

Attachment Content-Type Size
v2-0001-Minor-pg_overexplain-doc-adjustments.patch text/plain 1.6 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2025-07-16 21:23:27 Re: [PATCH] avoid double scanning in function byteain
Previous Message Andres Freund 2025-07-16 21:16:04 Re: index prefetching