Tom Lane wrote: > Bruce Momjian <[EMAIL PROTECTED]> writes: > > Because my EXECUTE example didn't work I have created a new example > > using date_trunc(), which I think is less error-prone than the > > comparisons done in the original example: > > This is not an improvement either. You can't represent the check > constraints that way (at least not if you want the planner to do > constraint exclusion with them) and I don't think it's "less > error-prone" to have a different representation in the trigger than > you have in the constraints.
I see, so date_trunc() can't be used for constraint exclusion in the CHECK constraint, and the trigger should match; makes sense. -- Bruce Momjian <[EMAIL PROTECTED]> http://momjian.us EnterpriseDB http://postgres.enterprisedb.com + If your life is a hard drive, Christ can be your backup. + ---------------------------(end of broadcast)--------------------------- TIP 5: don't forget to increase your free space map settings
