Re: SPI: ERROR: no snapshot has been set

Martijn van Oosterhout <kleptog@svana.org> writes:
>> I'm a bit concerned about the possible side-effects of this on existing
>> behavior, though.  In particular constructs like
>>    'now'::timestamp
>> would change behavior subtly.

> It's a good idea, eventually. All it would do is change the time it's
> evaluated, and in that example it doesn't change since 'now' is the
> transaction start time.

Well, it could change, eg if this appears in a PREPARE'd statement or a
column default expression.  Offhand it seems likely that the change
would be for the better, but I'm still hesitant.
        regards, tom lane