Re: need suggestion on querying big tables
От
Ron
Тема
Re: need suggestion on querying big tables
Дата
Msg-id
8c748c20-84bd-ed7b-c10f-35d640c6994b@gmail.com
Ответ на
Re: need suggestion on querying big tables (Holger Jakobs)
Список
Дерево обсуждения
need suggestion on querying big tables Ebin Jozer <ebinjozer@gmail.com>
Re: need suggestion on querying big tables Mladen Gogala <gogala.mladen@gmail.com>
Re: need suggestion on querying big tables John Wiencek <jwiencek3@comcast.net>
Re: need suggestion on querying big tables Samed YILDIRIM <samed@reddoc.net>
Re: need suggestion on querying big tables Ron <ronljohnsonjr@gmail.com>
Re: need suggestion on querying big tables Tom Lane <tgl@sss.pgh.pa.us>
Re: need suggestion on querying big tables Ron <ronljohnsonjr@gmail.com>
Re: need suggestion on querying big tables Scott Ribe <scott_ribe@elevated-dev.com>
Re: need suggestion on querying big tables Thomas Kellerer <shammat@gmx.net>
Re: need suggestion on querying big tables Holger Jakobs <holger@jakobs.com>
Re: need suggestion on querying big tables Ron <ronljohnsonjr@gmail.com>
Re: need suggestion on querying big tables Mladen Gogala <gogala.mladen@gmail.com>
Re: need suggestion on querying big tables Ebin Jozer <ebinjozer@gmail.com>
Re: need suggestion on querying big tables Bo Guo <bo.guo@gisticinc.com>
Re: need suggestion on querying big tables Paul Smith <paul@pscs.co.uk>
On 12/5/22 01:35, Holger Jakobs wrote:
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?
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 runningWe can see the wait event is IO and directDatafile .Server Spec : 8 cores and 64GB RAMPG 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,
EbinThere are basically two "secrets" to performance in this case:
- make sure that the join operation uses indexes
- 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.
Angular momentum makes the world go 'round.
В списке pgsql-admin по дате отправления