=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D
POSTGRESQL BUG REPORT TEMPLATE
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D
Your name : Nayib Kiuhan
Your email address : nayib@onlinetec.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=20
"date" timestamp DEFAULT 'now'=20=20=20
It use to works properly, placing the actual date at the moment a new recor=
d was inserted. Now it always have the same date which correspond to the da=
te at creating the table.
Please describe a way to repeat the problem. Please try to provide a
concise reproducible example, if at all possible:
----------------------------------------------------------------------
