Re: time stops within transaction

From: Alex Pilosov <alex(at)pilosoft(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: time stops within transaction
Date: 2000-10-19 02:24:04
Message-ID: Pine.BSO.4.10.10010182222560.22422-100000@spider.pilosoft.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, 18 Oct 2000, Tom Lane wrote:

> I think what you are advocating is recomputing now() at each statement
> boundary within a transaction, but that's not as simple as it looks
> either. 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)?

-alex

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Brian Edginton 2000-10-19 02:29:24 Re: [HACKERS] pg_connect error
Previous Message Larry Rosenman 2000-10-19 00:07:03 Re: [HACKERS] pg_connect error