Hi, David, On Tue, Aug 22, 2017 at 12:06 PM, David G. Johnston <david.g.johnston@xxxxxxxxx> wrote: > On Tue, Aug 22, 2017 at 8:43 AM, Igor Korot <ikorot01@xxxxxxxxx> wrote: >> >> Or this is the bug in 9.1? >> Since it looks like there are 2 columns with the same info in 1 >> table/view.... > > > This old email thread sounds similar to what you are describing here. > > https://www.postgresql.org/message-id/56D0C4B8.7020200%40aklaver.com Consider following table creation command: CREATE TABLE leaguescorehitter(id integer, playerid integer, scoreid integer, value double, foreign key(id) references leagues(id), foreign key(id, playerid) references playersinleague(id, playerid), foreign key(scoreid) references scorehits(scoreid)); There are 3 foreign keys in this table for which there are 4 rows displayed in my query as it should be: 1 for leagues(id) 1 for scorehits(scoreid) 2 for playersinleague(id,playerid) - 1 row per field However what I would expect to see is: [code] ordinal_position | position_in_unique_constraint 0 1 - this is for leagues(id) 1 1 1 2 - those 2 are for playersinleague(id,playerid) 2 1 - this is for scorehits(scoreid) [/code] Instead I got ordinal_positionv = position_in_unique_constraints and can't tell which constraint is which, or more precisely, when the one ends and second starts. Hopefully this above will not be mangled and the spacing will be kept. Thank you. > > David J. > -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
