"Jeroen Ruigrok/asmodai" <[EMAIL PROTECTED]> wrote:
> -On [20030911 15:43], Tom Lane ([EMAIL PROTECTED]) wrote:
> >We can't ALTER a table that's already in use when the first ALTER
> >starts, either --- its attempt to exclusive-lock the table will fail.
> >But once you get the exclusive lock, you can (in Postgres) perform
> >a series of operations without fear that subsequently-started
> >transactions will be able to see the incompletely changed state of the
> >table. Evidently Oracle can't handle that. That's why they need to
> >invent combination operations like MODIFY CONSTRAINT.
>
> As my colleague says:
>
> it is indeed a lazy choice, but super safe and that's the goal.
Does your colleague know the Aesops's Fables: "The fox and the Grapes" ?
Regards
Gaetano Mendola
---------------------------(end of broadcast)---------------------------
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faqs/FAQ.html
