Skip site navigation (1) Skip section navigation (2)

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 (view raw or flat)
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

pgsql-bugs by date

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

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group