>Toon Koppelaars <toon.koppelaars@xxxxxxxxxxx> >This makes me wonder then: how does PostgreSQL protect you from the indeterministic behaviour that your code can experience when writing queries on the (mutating) table inside row triggers? I knew someone must understand what this "imutable" property means. Can you explain in more details? Is it because "statement level isolation" requires that trigger (which executes "inside" the statement) see rows as they are "before statement started"? -- //www.freelists.org/webpage/oracle-l