On Thu, Jan 4, 2024 at 7:13 AM Jeff Janes wrote:
>
>
>> *1st time query executed with PARALLEL DEGREE 2 *
>> explain analyze select /*+* PARALLEL(A 2)* */ * from
>> test_compare_all_col_src1 A;
>>
>> QUERY PLAN
>>
>> ---
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 sligh
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/
lain| |
Indexes:
"test_compare_all_col_src1_pkey" PRIMARY KEY, btree (col_bigint)
Replica Identity: FULL
Access method: heap
# select count(*) from test_compare_all_col_src1;
count
955000
(1 row)
Thanks,
--Mohini
On Wed, 27 Dec 2023, 20:11 Jeff Janes, wrote:
>
Hello Team,
I observed that increasing the degree of parallel hint in the SELECT query
did not show performance improvements.
Below are the details of sample execution with EXPLAIN ANALYZE
*PostgreSQL Version:* v15.5
*Operating System details:* RHL 7.x
Architecture: x86_64
CPU op-mode(s):
