Re: BUG #1938: pg_dump mis-intreprets "default now()";

From: Jeff MacDonald <jeff(at)interchange(dot)ca>
To: Michael Fuhr <mike(at)fuhr(dot)org>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #1938: pg_dump mis-intreprets "default now()";
Date: 2005-10-06 12:35:27
Message-ID: 43451A0F.1080309@interchange.ca
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Thanks !

Jeff.

Michael Fuhr wrote:
> On Tue, Oct 04, 2005 at 08:29:23PM +0100, Jeff MacDonald wrote:
>
>>I did a backup from 7.3.2 using pg_dumpall.
>>
>>When I did a restore all of my timestamps that were defaulted to now(); were
>>now defaulted to the time that I piped my dump back into postgres.
>>
>>Meaning the now() was parsed instead of just being copied.
>
>
> Are you sure the default was now() and not 'now'? If you still
> have the 7.3.2 server running then check the table definitions.
> Aside from using psql's \d commands, you could do this:
>
> SELECT adrelid::regclass, adnum, adsrc
> FROM pg_attrdef
> ORDER BY adrelid, adnum;
>
> The 7.3 documentation warns against using 'now', and the 7.4 Release
> Notes mention a behavior change with respect to column defaults.
>
> http://www.postgresql.org/docs/7.3/interactive/functions-datetime.html#FUNCTIONS-DATETIME-CURRENT
> http://www.postgresql.org/docs/7.4/interactive/release-7-4.html
>

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Jaime Casanova 2005-10-06 15:29:03 Re: BUG #1940: Troubles with ODBC Clientes XP
Previous Message Juan Carlos Moreno G. 2005-10-05 23:05:42 BUG #1940: Troubles with ODBC Clientes XP