| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Martijn van Oosterhout <kleptog(at)svana(dot)org> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: SPI: ERROR: no snapshot has been set |
| Date: | 2005-08-13 17:09:34 |
| Message-ID: | 14238.1123952974@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Martijn van Oosterhout <kleptog(at)svana(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Fuhr | 2005-08-13 17:40:22 | Re: psql SET/RESET/SHOW tab completion |
| Previous Message | Tom Lane | 2005-08-13 17:05:27 | Re: psql SET/RESET/SHOW tab completion |