Re: BUG #1938: pg_dump mis-intreprets "default now()"; - Mailing list pgsql-bugs

From Michael Fuhr
Subject Re: BUG #1938: pg_dump mis-intreprets "default now()";
Date
Msg-id 20051005081311.GA54389@winnie.fuhr.org
Whole thread Raw
In response to BUG #1938: pg_dump mis-intreprets "default now()";  ("Jeff MacDonald" <jeff@interchange.ca>)
Responses Re: BUG #1938: pg_dump mis-intreprets "default now()";
List pgsql-bugs
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

--
Michael Fuhr

pgsql-bugs by date:

Previous
From: "Jeff MacDonald"
Date:
Subject: BUG #1938: pg_dump mis-intreprets "default now()";
Next
From: Bruce Momjian
Date:
Subject: Re: Bug?: Text after right paren in query is ignored