Search Postgresql Archives

Re: Improving performance of select query

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Subject: Re: Improving performance of select query
From: Rob Sargent <robjsargent@xxxxxxxxx>
Date: Mon, 14 Dec 2020 10:50:39 -0700
Cc: pgsql-general <pgsql-general@xxxxxxxxxxxxxxxxxxxx>
In-reply-to: <CAJqS1V+FrqZC7rQGe3wFVHa5UEz1RfnHPDa-15UkJjbRpKVEdg@mail.gmail.com>
References: <20c57bfb287749c2a5ff22d7ddd3df93@sandvine.com> <b9277405-f578-bab1-2d4b-ad46d60f8b8b@gmx.net> <93B14ED6-5AD1-4427-AED6-A4B80D27DD15@gmail.com> <CAJqS1V+FrqZC7rQGe3wFVHa5UEz1RfnHPDa-15UkJjbRpKVEdg@mail.gmail.com>

On Dec 14, 2020, at 10:37 AM, Muhammad Bilal Jamil <mbjamil92@xxxxxxxxx> wrote:

I think you can also increase the query performance by creating indexes?

OP said there was a key on the target (large) table. I’m not sure there’s much of a win in indexing 10K ids.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

References:
- Improving performance of select query
  - From: Karthik Shivashankar
- Re: Improving performance of select query
  - From: Thomas Kellerer
- Re: Improving performance of select query
  - From: Rob Sargent
- Re: Improving performance of select query
  - From: Muhammad Bilal Jamil

Prev by Date: Re: Improving performance of select query
Next by Date: PostgreSQL @ FOSDEM 2021 - Call for Papers
Previous by thread: Re: Improving performance of select query
Next by thread: Mitigating impact of long running read-only queries
Index(es):
- Date
- Thread

[Index of Archives] [Postgresql Jobs] [Postgresql Admin] [Postgresql Performance] [Linux Clusters] [PHP Home] [PHP on Windows] [Kernel Newbies] [PHP Classes] [PHP Books] [PHP Databases] [Postgresql & PHP] [Yosemite]

Powered by Linux