Re: So, why shouldn't SET CONSTRAINTS set a transaction snapshot?

Tom Lane wrote:

> 1. Always set a snapshot for SET CONSTRAINTS.  This is a minus-one-liner
> --- just remove it from the exclusion list in PortalRunUtility.
> 
> 2. Have it set a snapshot only if it finds pending trigger events to
> fire.  This would only require another half dozen lines of code, but
> it's certainly more complicated than choice #1.

It seems to me there is room for a backwards compatibility argument
here.  How about doing #2 for 8.3 and back, and #1 for 8.4?

-- 
Alvaro Herrera                                http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.