Re: improve SET CONSTRAINTS

Bruce Momjian wrote:
>
> Jan, we need a comment on this.

I don't recall all the bits and pieces, but looking at the patch it
seems to me that it would break SET CONSTRAINTS ALL DEFERRED. The if a
constraint is deferrable but not initially deferred, the changes look to
me that it'll not become so with this patch.

Also, don't we run the trigger queue after each statement anyway? So why
does it need to be run by SET CONSTRAINTS explicitly?

Jan

>
> ---------------------------------------------------------------------------
>
> Tom Lane wrote:
> > Neil Conway <nconway(at)klamath(dot)dyndns(dot)org> writes:
> > > Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:
> > >> I would assume that Jan and Stephan put that code in for a reason.
> >
> > > In that case, some documentation of its intended purpose would be
> > > nice.
> >
> > That's a fair complaint. I don't see any sign that that functionality
> > ever got documented, or even included in the regression tests. Jan?
> >
> > regards, tom lane
> >
> > ---------------------------(end of broadcast)---------------------------
> > TIP 1: subscribe and unsubscribe commands go to majordomo(at)postgresql(dot)org
> >
>
> --
> Bruce Momjian | http://candle.pha.pa.us
> pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
> + If your life is a hard drive, | 13 Roberts Road
> + Christ can be your backup. | Newtown Square, Pennsylvania 19073
>
> ---------------------------(end of broadcast)---------------------------
> TIP 5: Have you checked our extensive FAQ?
>
> http://www.postgresql.org/users-lounge/docs/faq.html

--

#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me. #
#================================================== JanWieck(at)Yahoo(dot)com #