Re: [PATCH] Incremental sort (was: PoC: Partial sort) - Mailing list pgsql-hackers

From Peter Geoghegan
Subject Re: [PATCH] Incremental sort (was: PoC: Partial sort)
Date
Msg-id CAH2-Wz=kbMtVnkwjR2BgypCZ0xZ=QL=Te8_7rCoW1mEymATeTg@mail.gmail.com
Whole thread Raw
In response to Re: [PATCH] Incremental sort (was: PoC: Partial sort)  (James Coleman <jtc331@gmail.com>)
List pgsql-hackers
On Thu, Jul 2, 2020 at 8:47 AM James Coleman <jtc331@gmail.com> wrote:
> It seems like the consensus over at another discussion on this topic
> [1] is that we ought to go ahead and print the zeros [for machine
> readable output formats], even though that creates some interesting
> scenarios like the fact that disk sorts will print 0 for memory even
> though that's not true.

What about having it print -1 for memory in this case instead? That's
still not ideal, but machine readable EXPLAIN output ought to
consistently show the same information per node, even when the answer
is in some sense indeterminate. That seems to be the standard that
we've settled on.

It might be worth teaching the JSON format to show a JSON null or
something instead. Not sure about that, though.

-- 
Peter Geoghegan



pgsql-hackers by date:

Previous
From: Thomas Munro
Date:
Subject: Re: Reducing WaitEventSet syscall churn
Next
From: Peter Eisentraut
Date:
Subject: Re: recovering from "found xmin ... from before relfrozenxid ..."