- Notifications
You must be signed in to change notification settings - Fork5
Commit33556af
committed
Fix errors in key_column_usage.position_in_unique_constraint column recently
added to information_schema (per a SQL2003 addition). The original codingfailed if a referenced column participated in more than one pg_constraintentry. Also, it did not work if an FK relied directly on a unique indexwithout any constraint syntactic sugar --- this case is outside the SQL spec,but PG has always supported it, so it's reasonable for our information_schemato handle it too. Per bug#2750 from Stephen Haberman.Although this patch changes the initial catalog contents, I didn't forceinitdb. Any beta3 testers who need the fix can install it via CREATE ORREPLACE VIEW, so forcing them to initdb seems an unnecessary imposition.1 parent87a5016 commit33556af
1 file changed
+32
-11
lines changedLines changed: 32 additions & 11 deletions
Original file line number | Diff line number | Diff line change | |
---|---|---|---|
| |||
4 | 4 |
| |
5 | 5 |
| |
6 | 6 |
| |
7 |
| - | |
| 7 | + | |
8 | 8 |
| |
9 | 9 |
| |
10 | 10 |
| |
| |||
52 | 52 |
| |
53 | 53 |
| |
54 | 54 |
| |
| 55 | + | |
| 56 | + | |
| 57 | + | |
| 58 | + | |
| 59 | + | |
| 60 | + | |
| 61 | + | |
| 62 | + | |
| 63 | + | |
| 64 | + | |
| 65 | + | |
| 66 | + | |
| 67 | + | |
| 68 | + | |
| 69 | + | |
| 70 | + | |
| 71 | + | |
| 72 | + | |
| 73 | + | |
| 74 | + | |
| 75 | + | |
| 76 | + | |
55 | 77 |
| |
56 | 78 |
| |
57 | 79 |
| |
| |||
922 | 944 |
| |
923 | 945 |
| |
924 | 946 |
| |
925 |
| - | |
926 |
| - | |
927 |
| - | |
928 |
| - | |
929 |
| - | |
930 |
| - | |
931 |
| - | |
| 947 | + | |
| 948 | + | |
| 949 | + | |
| 950 | + | |
| 951 | + | |
| 952 | + | |
932 | 953 |
| |
933 |
| - | |
| 954 | + | |
934 | 955 |
| |
935 |
| - | |
| 956 | + | |
936 | 957 |
| |
937 | 958 |
| |
938 | 959 |
| |
| |||
947 | 968 |
| |
948 | 969 |
| |
949 | 970 |
| |
950 |
| - | |
| 971 | + | |
951 | 972 |
| |
952 | 973 |
| |
953 | 974 |
| |
|
0 commit comments
Comments
(0)