Tom - Thanks for the response. I guess what I am really looking for is a
simple way to find all of the columns referenced from a given instance of a
table or index from the json file, although it would be even better if it
was easy to differentiate between the columns that came from the index vs
Jeff Janes writes:
> On Tue, Jan 2, 2024 at 1:29 PM Jerry Brenner wrote:
>> - It looks like "Output" includes more than just the columns with
>> predicates and/or being accessed or returned in other nodes.
> Not in my hands. For SELECTs it just lists the columns that are needed.
It depends.
On Tue, Jan 2, 2024 at 1:29 PM Jerry Brenner wrote:
> We are currently on 13.9.
>
Why not just use the latest minor release, 13.13? For security reasons,
that is the only minor release of v13 you should be using anyway. I think
it is a bit much to hope that people will spend their time for
We are currently on 13.9. For each of the questions, I'd also like to know
if anything has changed in that area in later releases.
NOTE: We are capturing all explain plans via auto_explain and storing them
in a database table. One of our longer term goals is to build the
relationship between
On Tue, 2 Jan 2024, 21:45 David G. Johnston,
wrote:
> On Tue, Jan 2, 2024 at 8:12 AM mohini mane
> wrote:
>
>>
>> I have executed the SELECT query with 2,4 & 6 parallel degree however
every time only 4 workers launched & there was a slight increase in
Execution time as well,
>>>
On Tue, Jan 2, 2024 at 8:12 AM mohini mane wrote:
>
> I have executed the SELECT query with 2,4 & 6 parallel degree however
>>> every time only 4 workers launched & there was a slight increase in
>>> Execution time as well,
>>>
>>
>> Adding an ignored comment to your SQL would not be expected to
On Fri, Dec 29, 2023 at 10:25 AM Jeff Janes wrote:
>
>
> On Thu, Dec 28, 2023 at 7:47 AM mohini mane
> wrote:
>
>> Thank you for your response !!
>> I am experimenting with SQL query performance for SELECT queries on large
>> tables and I observed that changing/increasing the degree of parallel
