Re: patch for check constraints using multiple inheritance
От | Robert Haas |
---|---|
Тема | Re: patch for check constraints using multiple inheritance |
Дата | |
Msg-id | AANLkTi=duKB_1L61ma5azRXWJxoZi7sH94E0mRRhGNz4@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: patch for check constraints using multiple inheritance (Yeb Havinga <yebhavinga@gmail.com>) |
Ответы |
Re: patch for check constraints using multiple inheritance
|
Список | pgsql-hackers |
On Fri, Jul 30, 2010 at 4:38 PM, Yeb Havinga <yebhavinga@gmail.com> wrote: >> I'm looking at ATPrepAddColumn right now, where there is actually some >> comments about getting the right attinhcount in the case of multiple >> inherited children, but it's the first time I'm looking at this part of >> PostgreSQL and it needs some time to sink in. It looks a bit like at the >> place of the comment /* child should see column as singly inherited */, >> maybe the recursion could be stopped there as well, i.e. not only setting >> inhcount to 1, but actually adding the child relation one time to the >> wqueue. > > I believe the crux is to stop double recursion from a parent in > ATOneLevelRecursion. I did a quick test by adding a globally defined > > static List *visitedrels = NIL; I agree that's the crux of the problem, but I can't see solving it with a global variable. I realize you were just testing... > PS: forgot to say thanks for looking into this problem earlier in the > thread. Thanks! yw -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise Postgres Company
В списке pgsql-hackers по дате отправления: