Re: Bug in pg_get_constraintdef (for deferrable constraints)
От | Stephan Szabo |
---|---|
Тема | Re: Bug in pg_get_constraintdef (for deferrable constraints) |
Дата | |
Msg-id | 20030101133815.Y81242-200000@megazone23.bigpanda.com обсуждение исходный текст |
Ответ на | Re: Bug in pg_get_constraintdef (for deferrable constraints) (Bruce Momjian <pgman@candle.pha.pa.us>) |
Ответы |
Re: Bug in pg_get_constraintdef (for deferrable
Re: Bug in pg_get_constraintdef (for deferrable constraints) Re: Bug in pg_get_constraintdef (for deferrable constraints) |
Список | pgsql-hackers |
On Wed, 1 Jan 2003, Bruce Momjian wrote: > Tom Lane wrote: > > Bruce Momjian <pgman@candle.pha.pa.us> writes: > > > I see the values being stored on constriant creation, but not being used > > > anywhere: > > > > I believe the values that actually get inspected at runtime are the > > tgdeferrable and tginitdeferred fields in pg_trigger. The columns in > > pg_constraint are just copies of these. > > > > It is not real clear to me whether it should be allowed to alter the > > deferrability status of a foreign-key constraint --- is that in the spec? > > The big problem is that while pg_dump's dump_trigger() looks at > tginitdeferred and dumps accordingly, pg_get_constraintdef doesn't look > at tginitdeferred, and therefore doesn't record the requirement as part > of ALTER TABLE ADD CONSTRAINT. pg_get_constraintdef should probably be looking at condeferrable and condeferred in the pg_constraint row it's looking at. Maybe something like the attached.
В списке pgsql-hackers по дате отправления: