From: Ron <ronljohnsonjr@gmail.com>
To: pgsql-admin@lists.postgresql.org
Subject: Re: need suggestion on querying big tables
Date: Mon, 5 Dec 2022 08:45:08 -0600
Message-ID: <8c748c20-84bd-ed7b-c10f-35d640c6994b@gmail.com> (raw)
In-Reply-To: <ec145210-d879-df91-ebc8-8ad2f5643e4b@jakobs.com>
References: <CAJuN1jj6NQDUjbMH=n4zry10JMJEZ8bRi=j6uA-3_108-Tq9cQ@mail.gmail.com>
<ec145210-d879-df91-ebc8-8ad2f5643e4b@jakobs.com>
On 12/5/22 01:35, Holger Jakobs wrote:
> Am 05.12.22 um 07:29 schrieb Ebin Jozer:
>> Hi Team,
>> in postgresql 11 version we have two tables of size 435 GB and 347 GB.
>> if we query on single table or if we are doing inner join on both the big
>> tables, it is not displacing any output, it keeps running
>>
>> We can see the wait event is IO and directDatafile .
>>
>> Server Spec : 8 cores and 64GB RAM
>> PG config : 53 GB(effective_cache), 12 GB(shared buffer)
>>
>> can you please suggest some ideas , how we can query on big tables and
>> fasten them to get the output??
>>
>> Thanks & Regards,
>> /Ebin/
>
> There are basically two "secrets" to performance in this case:
>
> 1. make sure that the join operation uses indexes
> 2. make sure that you have enough work_mem available
>
> work_mem can be set in postgresql.conf, but also in every session
> individually. So don't set it too high generally, because it will be
> allocated for every sorting and hashing operation.
>
A "just smart enough" user could perform an inadvertent Denial of Service
attack on the database by cranking his session work_mem really high, no?
--
Angular momentum makes the world go 'round.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: ronljohnsonjr@gmail.com, pgsql-admin@lists.postgresql.org
Subject: Re: need suggestion on querying big tables
In-Reply-To: <8c748c20-84bd-ed7b-c10f-35d640c6994b@gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox