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 1szEsF-004zPy-48 for pgsql-admin@arkaria.postgresql.org; Fri, 11 Oct 2024 12:36:03 +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 1szEsC-003Ijp-0a for pgsql-admin@arkaria.postgresql.org; Fri, 11 Oct 2024 12:36:00 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1szEsB-003Ijf-Ln for pgsql-admin@lists.postgresql.org; Fri, 11 Oct 2024 12:36:00 +0000 Received: from mail-qk1-x72a.google.com ([2607:f8b0:4864:20::72a]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1szEs9-000Mfg-6F for pgsql-admin@lists.postgresql.org; Fri, 11 Oct 2024 12:35:58 +0000 Received: by mail-qk1-x72a.google.com with SMTP id af79cd13be357-7b11704601cso104309485a.3 for ; Fri, 11 Oct 2024 05:35:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1728650156; x=1729254956; 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=MdsDOKR7N+iuwRA3ms/WjLQqsPlQylv7bC6abXU4uok=; b=JJUt761Y9zrKeZvj2t39l2A6ayYMcCjHdkAnw4lK1toXZRE4B8bKIUiqk3GsbRacpq ygxRDE1pXSPiFq4Xskmjx8mTIMndtgVFT0S1QgweCQQZzoVrFHKhOg/xG8+o907/8SAh loWo6SxBqDGppoqw7cUlPFRDrhmSUjyGR1kRGLBcnE9lMM0aWPi9CTQ436j3eJ5QlGA3 qSIE9twibhOFvUX9ZGcLtJ4q24TckC+IR7Nt59538s07Jw1CXy0aWGXH7xIFXvzpYi2V Luzd3H1vH0QEBx32kXZ6OidUuCz+ApMUx0wm/Fdz3EbEjTSisntEAWhlymkWURBWszhT 28OA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1728650156; x=1729254956; 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=MdsDOKR7N+iuwRA3ms/WjLQqsPlQylv7bC6abXU4uok=; b=ui+dTDUYcZbrQQTf7zYvEwPXbwC3sn1ltJ0vB7NDkOBtFKamCss/hOFqReMp1+QwHB b9caTPLbt1xOtLHlV+3snJjoXiGavQSK8PsCcFKAhHgBHANegivmHYfhwK+dfEM2YC9Q TkRiL+Gx1gumLJ+sujkExLn4YHIa+p7hh9KR69kHDgmrvU3jeTlxBoeu76WUt2zPi3kJ sxvVB8jkBHnKySJRtN1s3X+VpDz132R3YnY75CO43CA2+WxpZ/y1jPeUi13CuJVKWzKC 6awLaU6aDwtvK9KsWRMzDxoRpHH+CQlIWBp2gVXV1TR9p0oDVdHTABWg+K6Sh4r11sBm pcCw== X-Gm-Message-State: AOJu0YyhXChcfRYrVQcMqRLcFijbV2K+fH9c/GgfQkT+rHDkHgBfiAe7 f4zc3U6ZvxLtj/i+sLWOYipa8ntS6DgdNIq3LxPYOZSgLEMbaHDm8uZbuo+KWiB6AqfhWbh5aAi WHcXdZqWIwjKnCEnQZtmQshNOODM= X-Google-Smtp-Source: AGHT+IGQTz8z2qVtGFj4Ky8XMbInPiguP46EXM8531qDjv09y1DloH1g+nZEd4zT/MvrOthD0Dx52hsuPKzfdCGZf5M= X-Received: by 2002:a0c:fa0c:0:b0:6cb:f6a6:55a8 with SMTP id 6a1803df08f44-6cbf6a655d4mr10968976d6.27.1728650156262; Fri, 11 Oct 2024 05:35:56 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Avinash Vallarapu Date: Fri, 11 Oct 2024 16:35:44 +0400 Message-ID: Subject: Re: Direct particular index use as like oracle To: Sathish Reddy Cc: pgsql-admin Content-Type: multipart/alternative; boundary="000000000000814f2d062432ba88" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000814f2d062432ba88 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi, On Fri, Oct 11, 2024, 4:24 PM Sathish Reddy < sathishreddy.postgresql@gmail.com> wrote: > Yes, that is correct. > Okay. You might have to provide some more information to get more help such as, the SQL, it's Query Plan and Table DDL. If you have migrated this table from Oracle, you might have to perform a Vacuum Analyze on this table before you try anything. Vacuum analyze ; On Fri, Oct 11, 2024, 5:50=E2=80=AFPM Avinash Vallarapu > wrote: > >> Hi, >> >> On Fri, Oct 11, 2024, 2:59 PM Sathish Reddy < >> sathishreddy.postgresql@gmail.com> wrote: >> >>> Hi >>> We see direct use particular index in oracle.same we are trying to us= e >>> in postgres.but every time we ae getting failed.please help us. >>> >> Do you mean that you don't see an Index being considered by planner in >> Postgres, whereas a similar index is used in Oracle ? >> >> If the above is yes, can you provide some more information? >> >> >>> >>> Thanks >>> Sathish Reddy >>> >> >> >> Regards, >> Avi. >> >> Try HexaRocket today for your Oracle to PostgreSQL Migrations. >> >> www.hexarocket.com >> >>> --000000000000814f2d062432ba88 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi,=C2=A0

On Fri, Oct 11, 2024, 4:24 PM Sathish Reddy &= lt;sathishreddy.postgr= esql@gmail.com> wrote:

Yes, that is correct.

Okay. You might have to provide some more information to get more help s= uch as, the SQL, it's Query Plan and Table DDL.
=
If you have migrated this table from Oracle, yo= u might have to perform a Vacuum Analyze on this table before you try anyth= ing.

Vacuum analyze <= table>;


On Fri, Oct = 11, 2024, 5:50=E2=80=AFPM Avinash Vallarapu <avinash.vallarapu@= gmail.com> wrote:
Hi,=C2=A0

On Fri, Oct 11, 2024, 2:59 PM Sathish Reddy <sathishreddy.postgresql@gmail.com> wrote:
Hi
= =C2=A0 We see direct use particular index in oracle.same we are trying to u= se in postgres.but every time we ae getting failed.please help us.
Do you mean that you don'= t see an Index being considered by planner in Postgres, whereas a similar i= ndex is used in Oracle ?=C2=A0

If the above is yes, can you provide some more=C2=A0information?

=


Thanks=C2=A0
Sathish Reddy=C2=A0


Regards,<= /div>
Avi.=C2=A0

Try HexaRocket today for your Oracle to PostgreSQL Migrations.=C2= =A0

--000000000000814f2d062432ba88--