pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: John Wiencek <jwiencek3@comcast.net>
To: Ebin Jozer <ebinjozer@gmail.com>
Cc: pgsql-admin <pgsql-admin@lists.postgresql.org>
Subject: Re: need suggestion on querying big tables
Date: Mon, 5 Dec 2022 08:50:17 -0600
Message-ID: <74322C20-BFDD-484A-9566-1644480F8253@comcast.net> (raw)
In-Reply-To: <CAJuN1jj6NQDUjbMH=n4zry10JMJEZ8bRi=j6uA-3_108-Tq9cQ@mail.gmail.com>
References: <CAJuN1jj6NQDUjbMH=n4zry10JMJEZ8bRi=j6uA-3_108-Tq9cQ@mail.gmail.com>

Verify that your statistics are current.


John

> On Dec 5, 2022, at 12:29 AM, Ebin Jozer <ebinjozer@gmail.com> wrote:
> 
> 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

view thread (15+ messages)  latest in thread

Message-ID: <74322C20-BFDD-484A-9566-1644480F8253@comcast.net>
Permalink:  ../74322C20-BFDD-484A-9566-1644480F8253@comcast.net/
Also on:    postgresql.org/message-id/74322C20-BFDD-484A-9566-1644480F8253@comcast.net

 · 

reply

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: jwiencek3@comcast.net, ebinjozer@gmail.com, pgsql-admin@lists.postgresql.org
  Subject: Re: need suggestion on querying big tables
  In-Reply-To: <74322C20-BFDD-484A-9566-1644480F8253@comcast.net>

* 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