MIME-Version: 1.0
References: <CAD=mzVWLN35FHPxN0Ajh2vnDkFLyg9f0vT6EKF9uPm7CYkHS5g@mail.gmail.com>
 <88e5c335-c70e-4973-9b71-6c12e251e5b7@ewie.name> <CAD=mzVWHC8O+fLksgc-uKAcq19xQSVvHz1AsButFmL+xh0_btg@mail.gmail.com>
 <CAKAnmmJW_pmtYLPyO2MONF+L_Wz_8kgPZE881cHPzd7MScrsXA@mail.gmail.com>
 <CAJCZko+-DCLp75-9JvkYxjrnvFqCA++VN1yLhFgwCYJWvqp8rA@mail.gmail.com> <CAKAnmmKORn7S+Nc6Pr1y57hV2G833F6QyM9vhdFeoAZmTmdnSw@mail.gmail.com>
In-Reply-To: <CAKAnmmKORn7S+Nc6Pr1y57hV2G833F6QyM9vhdFeoAZmTmdnSw@mail.gmail.com>
From: Durgamahesh Manne <maheshpostgres9@gmail.com>
Date: Fri, 11 Oct 2024 19:07:30 +0530
Message-ID: <CAJCZkoKAhQ2VC-eA4zWgxfW5nTAA2N4V5vrsWFXHPVvVg0WdfQ@mail.gmail.com>
Subject: Re: Question on indexes
To: Greg Sabino Mullane <htamfids@gmail.com>
Cc: sud <suds1434@gmail.com>, Erik Wienhold <ewie@ewie.name>, xof@thebuild.com, 
	pgsql-general <pgsql-general@lists.postgresql.org>
Content-Type: multipart/alternative; boundary="0000000000004cf3f60624338b44"
Archived-At: <https://www.postgresql.org/message-id/CAJCZkoKAhQ2VC-eA4zWgxfW5nTAA2N4V5vrsWFXHPVvVg0WdfQ%40mail.gmail.com>
Precedence: bulk

--0000000000004cf3f60624338b44
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Fri, Oct 11, 2024 at 6:18=E2=80=AFPM Greg Sabino Mullane <htamfids@gmail=
.com>
wrote:

> (please start a new thread in the future rather than replying to an
> existing one)
>
> You cannot query on b and use an index on (a,b) as you observed. However,
> you can have two indexes:
>
> index1(a)
> index2(b)
>
> Postgres will be able to combine those when needed in the case where your
> WHERE clause needs to filter by both columns. So then you no longer need
> the two-column index.
>
> Cheers,
> Greg
>


Hi greg

Mail sent you with a new thread. composite key is on partitioned table

Regards,
Durga Mahesh

--0000000000004cf3f60624338b44
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><br></div><br><div class=3D"gmail_quote">=
<div dir=3D"ltr" class=3D"gmail_attr">On Fri, Oct 11, 2024 at 6:18=E2=80=AF=
PM Greg Sabino Mullane &lt;<a href=3D"mailto:htamfids@gmail.com">htamfids@g=
mail.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D=
"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-le=
ft:1ex"><div dir=3D"ltr">(please start a new thread in the future rather th=
an replying to an existing one)<div><br></div><div>You cannot query on b an=
d use an index on (a,b) as you observed. However, you can have two indexes:=
</div><div><br></div><div>index1(a)</div><div>index2(b)</div><div><br></div=
><div>Postgres will be able to combine those when needed in the case where =
your WHERE clause needs to filter by both columns. So then you no longer ne=
ed the two-column index.</div><div><br></div><div>Cheers,</div><div>Greg</d=
iv><div></div></div></blockquote><div><br></div><div>=C2=A0</div><div>Hi gr=
eg=C2=A0</div><div><br></div><div>Mail sent you with a new thread. composit=
e key is on partitioned table=C2=A0</div><div><br></div><div>Regards,</div>=
<div>Durga Mahesh=C2=A0=C2=A0<br></div></div></div>

--0000000000004cf3f60624338b44--