Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1szEto-004zYR-8s for pgsql-admin@arkaria.postgresql.org; Fri, 11 Oct 2024 12:37:40 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1szEtm-003N1o-II for pgsql-admin@arkaria.postgresql.org; Fri, 11 Oct 2024 12:37:38 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1szEtm-003N1g-1y for pgsql-admin@lists.postgresql.org; Fri, 11 Oct 2024 12:37:38 +0000 Received: from mail-ot1-x32c.google.com ([2607:f8b0:4864:20::32c]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1szEti-000VtR-IY for pgsql-admin@lists.postgresql.org; Fri, 11 Oct 2024 12:37:37 +0000 Received: by mail-ot1-x32c.google.com with SMTP id 46e09a7af769-716a5b30089so99344a34.3 for ; Fri, 11 Oct 2024 05:37:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=foresightweb-net.20230601.gappssmtp.com; s=20230601; t=1728650253; x=1729255053; darn=lists.postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=zQE9kFmLCmTJT0uStGCF4JarBkfVwEAvgoqF6dbGPZM=; b=LH3NeVMR+LYSSItco1f4WcqaVqrd5avKRP4ZLgFD8sjKDP+fs525JDR9CVcveROeDV elLVjYV5l80jh0QN3wt2i8x4ggC/n3LQKt40OP/BPBSRpdJDS7zrR4sKjjACp1ZYNKyl 9EvhkaHManNEtFTEC6UDJY9Y/xl+lrjFMnGkT+NNAAuyjxR/9x6Lp90ugl+FyA9IueiT FpBfvjNujMUe8FW07cR0XKK5fq2DeR+XyZfr+KxPY4wXcCUFXxO8yfHSwSmtnycvdYlU 54TUZ0cAjDaCpBSaJf0PgjFZ+pMh+H+/NJLb7Lms48MZ3FLYHlr9YOrNqXPe1wGjBT5g TGhQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1728650253; x=1729255053; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=zQE9kFmLCmTJT0uStGCF4JarBkfVwEAvgoqF6dbGPZM=; b=vFAWnlx6orwTixpi1hyBwJ7fq2DHgo3wdkD+gkNZ9xUA98h80xPkmRE//sUERU1+ve bggGZRLFtxwq5/lk4oR3lLdJIL1pgeSMbdlOGBLMYTRRw++DRwxz/jvYZkFLN7IzBh7E IiMzhY+gSA7P5dchnIrbLruDvfICzt2U2MbxJAF6MA6/QnQitMFliX14wg3SC4YZ7znJ E0muyhYcz7v0Y+7jkvMEmpe5sTuyydD2xJzdpHUU22D/r/MKnsvpp9YC9H3CVFx+n4xp cTGiAMtdFtGAcYvzu8NrYF1bXPMRoQC53xrPSo15MsBDyY6R/aRY4aJ2MAiYvA0WLaXI I8Vw== X-Gm-Message-State: AOJu0YwwB62Kc4TBeI2Z29lsuEZrIiJV/VhKvQm/1InWwQWgIjGxnsj6 1HmWS88kNFc3Pvd6TZodKpF11hkioyb+RSlZpjfLGJ88pzXkKjHrAuUPvURvi6fH7CPHfyeBbR2 0NYDltCPF7Hsp6slSSpzOBNaYHNyo09epYXu6Kw== X-Google-Smtp-Source: AGHT+IHGEeIDPZSFkNJKydKztN/PTpAQ9Npi70cJh4W3Ul6gEWSTvIiBH0tTsUcVZKAbKMucIsGfmH8j5SYmmC5dcfo= X-Received: by 2002:a05:6830:3113:b0:703:7a74:b7b7 with SMTP id 46e09a7af769-717d63e9380mr638863a34.2.1728650253378; Fri, 11 Oct 2024 05:37:33 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Keith Date: Fri, 11 Oct 2024 08:36:57 -0400 Message-ID: Subject: Re: Direct particular index use as like oracle To: Sathish Reddy Cc: pgsql-admin@lists.postgresql.org Content-Type: multipart/alternative; boundary="0000000000004b4ad7062432c0e0" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000004b4ad7062432c0e0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Fri, Oct 11, 2024 at 6:59=E2=80=AFAM Sathish Reddy < sathishreddy.postgresql@gmail.com> wrote: > Hi > We see direct use particular index in oracle.same we are trying to use > in postgres.but every time we ae getting failed.please help us. > > > Thanks > Sathish Reddy > There are no query hints in Postgres to direct it to use a particular index. Often it's the query itself that can be tuned to fix this happening or the ideal plan is actually being used vs the index you think you expect it should use. Share the query plan and table structure and people might be able to help you out more. --0000000000004b4ad7062432c0e0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


=
On Fri, Oct 11, 2024 at 6:59=E2=80=AF= AM Sathish Reddy <s= athishreddy.postgresql@gmail.com> wrote:
Hi
=C2= =A0 We see direct use particular index in oracle.same we are trying to use = in postgres.but every time we ae getting failed.please help us.


Thanks= =C2=A0
Sathish Reddy=C2=A0
<= div>
There are no query hints in Postgres to direct it to use= a particular index. Often it's the query itself that can be tuned to f= ix this happening or the ideal plan is actually being used vs the index you= think you expect it should use.

Share the query p= lan and table structure and people might be able to help you out more.
=
--0000000000004b4ad7062432c0e0--