| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Mike Mascari <mascarm(at)mascari(dot)com> |
| Cc: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Yury Bokhoncovich <byg(at)center-f1(dot)ru>, Dan Langille <dan(at)langille(dot)org>, Roland Roberts <roland(at)astrofoto(dot)org>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: (Fwd) Re: Any Oracle 9 users? A test please... |
| Date: | 2002-10-02 17:19:11 |
| Message-ID: | 24221.1033579151@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Mike Mascari <mascarm(at)mascari(dot)com> writes:
> SQL> CREATE PROCEDURE test
> 2 AS
> 3 BEGIN
> 4 INSERT INTO foo SELECT SYSDATE FROM dual;
> 5 dbms_lock.sleep(5);
> 6 INSERT INTO foo SELECT SYSDATE FROM dual;
> 7 END;
> 8 /
> Procedure created.
> SQL> execute test;
> PL/SQL procedure successfully completed.
> SQL> select to_char(a, 'HH24:MI:SS') from foo;
> TO_CHAR(
> --------
> 12:01:07
> 12:01:12
What fun. So in reality, SYSDATE on Oracle behaves like timeofday():
true current time. That's certainly not a spec-compliant interpretation
for CURRENT_TIMESTAMP :-(
Has anyone done the corresponding experiments on the other DBMSes to
identify exactly when they allow CURRENT_TIMESTAMP to advance?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Manfred Koizar | 2002-10-02 19:52:46 | Correlation in cost_index() |
| Previous Message | Oleg Bartunov | 2002-10-02 17:17:21 | DBD::PG - any works to be compatile with 7.3 ? |