Tom Lane wrote:
> Alex Pilosov <[EMAIL PROTECTED]> writes:
> >> Consider statement boundaries in an SQL function --- the
> >> function is probably being called from some outer statement, so
> >> advancing now() within the function would violate the spec constraint
> >> with respect to the outer statement.
> > Postgres doesn't have an idea of what a 'top-level' statement is? I.E.
> > statement as submitted by a client (libpq)?
>
> There's never been any reason to make such a distinction.
There's already a distinction.
Snapshot is made per top-level statement and functions/subqueries
use the same snapshot as that of top-level statement.
Regards.
Hiroshi Inoue
- Re: [HACKERS] time stops within transaction Tom Lane
- Re: [HACKERS] time stops within transaction Peter Eisentraut
- Re: [HACKERS] time stops within transaction Tom Lane
- Re: [HACKERS] time stops within transaction Peter Eisentraut
- Re: [HACKERS] time stops within transact... Tom Lane
- Re: [HACKERS] time stops within tra... Peter Eisentraut
- Re: [HACKERS] time stops within tra... Don Baccus
- Re: [HACKERS] time stops within tra... Alex Pilosov
- Re: [HACKERS] time stops within... Tom Lane
- Re: [HACKERS] time stops within... Hiroshi Inoue
- Re: [HACKERS] time stops within... Tom Lane
- Re: [HACKERS] time stops within... Hiroshi Inoue
- Re: [HACKERS] time stops within... Vadim Mikheev
- Re: [HACKERS] time stops within... Hiroshi Inoue
- Re: [HACKERS] time stops within... Tom Lane
- Re: [HACKERS] time stops within... Vadim Mikheev
- Re: [HACKERS] time stops within... Hiroshi Inoue
- RE: [HACKERS] time stops within... Hiroshi Inoue
- Re: [HACKERS] time stops within transaction Karel Zak
- Re: [HACKERS] time stops within transaction Mikheev, Vadim