Thread

1. pg_dump bug with default date

   Bryan White <bryan@arcamax.com> — 1999-03-10T20:27:59Z

   I use pg_dump to back up my database.  I recently changed one of my date
   fields to have a default value as such:
       firstcontactdate date default current_date,
   
   If I pg_dump the database and reload the CREATE statment for this table
   fails.  pg_dump used this defintion:
       "firstcontactdate" "date" DEFAULT date 'current'::datetime + '0 sec'),
   PSQL reports:
       ERROR:  parser: parse error at or near "'"
   
   I can work around this problem by extracting the offending the table create
   statement from the script, pre-creating the table with a corrected
   definition and ignoring the error when the script tries to create the table.
   I don't want to edit the script directly because it is 50MB and growing.
   Fortunately the schema statements are all at the front so I can grab them
   with "head -1000".
   
   This is Postgres 6.4.0.  Is this a known problem?  Has it been fixed?
   
   Bryan White
   ArcaMax Inc.
   Yorktown VA
   www.arcamax.com
   
   
   

2. Re: [GENERAL] pg_dump bug with default date

   Kevin Heflin <kheflin@shreve.net> — 1999-03-10T23:20:19Z

   On Wed, 10 Mar 1999, Bryan White wrote:
   
   > I use pg_dump to back up my database.  I recently changed one of my date
   > fields to have a default value as such:
   >     firstcontactdate date default current_date,
   > 
   > If I pg_dump the database and reload the CREATE statment for this table
   > fails.  pg_dump used this defintion:
   >     "firstcontactdate" "date" DEFAULT date 'current'::datetime + '0 sec'),
   > PSQL reports:
   >     ERROR:  parser: parse error at or near "'"
   > 
   > I can work around this problem by extracting the offending the table create
   > statement from the script, pre-creating the table with a corrected
   > definition and ignoring the error when the script tries to create the table.
   > I don't want to edit the script directly because it is 50MB and growing.
   > Fortunately the schema statements are all at the front so I can grab them
   > with "head -1000".
   
   
   
   I ran into this same problem with Postgres6.3x
   
   
   
   
   
   
   
   
   --------------------------------------------------------------------
   Kevin Heflin          | ShreveNet, Inc.      | Ph:318.222.2638 x103
   VP/Mac Tech           | 333 Texas St #619    | FAX:318.221.6612
   kheflin@shreve.net    | Shreveport, LA 71101 | http://www.shreve.net
   --------------------------------------------------------------------