| From: | Hannu Krosing <hannu(at)tm(dot)ee> |
|---|---|
| To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Neil Conway <neilc(at)samurai(dot)com>, Will LaShell <will(at)lashell(dot)net>, Christopher Browne <cbbrowne(at)acm(dot)org>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: start of transaction (was: Re: [PERFORM] Help with |
| Date: | 2003-11-17 10:19:06 |
| Message-ID: | 1069064346.20092.27.camel@fuji.krosing.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-performance |
Bruce Momjian kirjutas E, 17.11.2003 kell 02:31:
> Defining now() as the first call seems pretty arbitrary to me. I can't
> think of any time-based interface that has that API. And what if a
> trigger called now() in an earlier query and you didn't even know about
> it.
That would be OK. The whole point of that previous discussion was to
have now() that returns the same value over the span of the whole
transaction.
It would be even better to have now() that returns the time current
transaction is COMMITted as this is the time other backend become aware
of it ;)
-----------
Hannu
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hannu Krosing | 2003-11-17 10:28:34 | Re: [PATCHES] SRA Win32 sync() code |
| Previous Message | Hannu Krosing | 2003-11-17 10:16:06 | Re: start of transaction (was: Re: [PERFORM] Help with |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Shridhar Daithankar | 2003-11-17 10:43:28 | Re: start of transaction |
| Previous Message | Hannu Krosing | 2003-11-17 10:16:06 | Re: start of transaction (was: Re: [PERFORM] Help with |