MIME-Version: 1.0
References: 
 <CA+FnnTz7+dbyk5Gn2iM-eo1Xvfax15yjBevmCCfvo0-UVW1K7Q@mail.gmail.com>
 <b3f6ecfb-8772-4e15-a772-8e64fb573d49@aklaver.com>
 <CAKFQuwYswndGOm6vnsoNSTWHEC5d29bvYokymtDEY_cyW54FEQ@mail.gmail.com>
 <CA+FnnTyFVn4Ebx9kP-5vooZwpATwV5Euc8Nt6TGmEuR6oDYd9A@mail.gmail.com>
 <3547f40b-08b9-4d0c-bba8-f1c26d0bf09d@aklaver.com>
 <CA+FnnTwLvp1wweqWJkw1+sg4x+pM_oGVmfc-3TaPpE_557=A_A@mail.gmail.com>
 <2c31c118-7f8a-4359-9c4f-4cabd9df4262@aklaver.com>
 <CA+FnnTx5WZeYwg-OFwvbipvHRJP263UP8EVNY0aGMu6E_XuKsQ@mail.gmail.com>
 <7461c77a-4536-4f53-b951-99b9ca33db79@aklaver.com>
 <CA+FnnTw+HhguiTO27hzTUTU6uRBY_wRRwB=xT+7=t_0CdrCsoA@mail.gmail.com>
 <105a9d1a-c219-401a-9b81-4d77dde901f5@aklaver.com>
 <da939085-813e-4505-880d-aafa91c8509d@aklaver.com>
In-Reply-To: <da939085-813e-4505-880d-aafa91c8509d@aklaver.com>
From: Igor Korot <ikorot01@gmail.com>
Date: Mon, 16 Mar 2026 14:51:22 -0700
Message-ID: 
 <CA+FnnTxh0ZvsaKvkpg7OLQBVhhicsv2u+uk9d0jf+qmF5q=YTw@mail.gmail.com>
Subject: Re: Does included columns part of the PK
To: Adrian Klaver <adrian.klaver@aklaver.com>
Cc: pgsql-general <pgsql-general@postgresql.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: 
 <https://www.postgresql.org/message-id/CA%2BFnnTxh0ZvsaKvkpg7OLQBVhhicsv2u%2Buk9d0jf%2BqmF5q%3DYTw%40mail.gmail.com>
Precedence: bulk

Adrian,

On Mon, Mar 16, 2026 at 2:40=E2=80=AFPM Adrian Klaver <adrian.klaver@aklave=
r.com> wrote:
>
> On 3/16/26 2:30 PM, Adrian Klaver wrote:
> > On 3/16/26 11:47 AM, Igor Korot wrote:
> >
> > Reply to list also.
> > Ccing list.
> >> Adrian,
> >>
> >>
> >>
> >> On Mon, Mar 16, 2026, 8:03=E2=80=AFAM Adrian Klaver <adrian.klaver@akl=
aver.com
> >> <mailto:adrian.klaver@aklaver.com>> wrote:
> >>
> >>     On 3/15/26 6:23 PM, Igor Korot wrote:
> >>      > Hi, Adrian,
> >>      >
> >>      > Here is the log file from running in ODBC mode: https://bpa.st/
> >>     Z2DWG <https://bpa.st/Z2DWG>
> >>
> >>     I have no idea what this is trying to show?
> >>
> >>
> >> The log shows ODBC connection and then at the end - call to
> >> SQLPrimaryKeys().
> >
> > Where?
> >
> > I don't see that in either the link you posted or the text file Greg
> > sent to the list.
> >
> >>
> >> If you run it against the table I posted above, you will get 3 fields.
> >> Whereas it should be just one.
> >
> > Again, run it how?
>
> Alright I see what you are talking about now. I'm not using the ODBC
> driver just it's query. In psql :
>
> CREATE TABLE leagues_new (
>      id serial,
>      name varchar(100),
>      drafttype smallint,
>      scoringtype smallint,
>      roundvalues smallint,
>      leaguetype char(5),
>      salary integer,
>      benchplayers smallint,
>      PRIMARY KEY (id) INCLUDE (drafttype, scoringtype
> ) WITH (fillfactor =3D 50, deduplicate_items =3D OFF)
> );
>
>
> SELECT
>      ta.attname,
>      ia.attnum,
>      ic.relname,
>      n.nspname,
>      tc.relname
> FROM
>      pg_catalog.pg_attribute ta,
>      pg_catalog.pg_attribute ia,
>      pg_catalog.pg_class tc,
>      pg_catalog.pg_index i,
>      pg_catalog.pg_namespace n,
>      pg_catalog.pg_class ic
> WHERE
>      tc.relname =3D 'leagues_new'
>      AND n.nspname =3D 'public'
>      AND tc.oid =3D i.indrelid
>      AND n.oid =3D tc.relnamespace
>      AND i.indisprimary =3D 't'
>      AND ia.attrelid =3D i.indexrelid
>      AND ta.attrelid =3D i.indrelid
>      AND ta.attnum =3D i.indkey[ia.attnum - 1]
>      AND (NOT ta.attisdropped)
>      AND (NOT ia.attisdropped)
>      AND ic.oid =3D i.indexrelid
> ORDER BY
>      ia.attnum;
>
> yields
>
> attname   | attnum |     relname      | nspname |   relname
> -------------+--------+------------------+---------+-------------
>   id          |      1 | leagues_new_pkey | public  | leagues_new
>   drafttype   |      2 | leagues_new_pkey | public  | leagues_new
>   scoringtype |      3 | leagues_new_pkey | public  | leagues_new

Correct.

And according to the second reply it should yeld just the first record.

I'm going to forward this to the ODBC list...

Thank you.

>
>
> >
> >>
> >> Thank you.
> >>
>
>
> --
> Adrian Klaver
> adrian.klaver@aklaver.com