timestamp bug 7.4beta3

From: "Nayib Kiuhan" <nayib(at)onlinetec(dot)net>
To: <pgsql-bugs(at)postgresql(dot)org>
Subject: timestamp bug 7.4beta3
Date: 2003-10-15 06:08:40
Message-ID: 016f01c392e2$c7dbc980$6e01030a@xxx
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

============================================================================
POSTGRESQL BUG REPORT TEMPLATE
============================================================================

Your name : Nayib Kiuhan
Your email address : nayib(at)onlinetec(dot)net

System Configuration
---------------------
Architecture (example: Intel Pentium) : Sun Sparc IIIi

Operating System (example: Linux 2.0.26 ELF) : Solaris 9

PostgreSQL version (example: PostgreSQL-7.3): PostgreSQL-7.4beta3

Compiler used (example: gcc 2.95.2) : gcc 3.3

Please enter a FULL description of your problem:
------------------------------------------------
In versions before 7.4beta3 I use to have tables with
"date" timestamp DEFAULT 'now'
It use to works properly, placing the actual date at the moment a new record was inserted. Now it always have the same date which correspond to the date at creating the table.

Please describe a way to repeat the problem. Please try to provide a
concise reproducible example, if at all possible:
----------------------------------------------------------------------

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tomas Szepe 2003-10-15 14:33:40 Re: timestamp bug 7.4beta3
Previous Message Tom Lane 2003-10-14 18:42:53 Re: Bug in the information_schema.referential_constraints view