pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Mark Stosberg <mark@summersault.com>
To: pgsql-sql@postgresql.org
Subject: CURRENT_TIMESTAMP breaking with 7.1->7.2 dump/import
Date: Tue, 19 Feb 2002 17:04:01 -0500
Message-ID: <3C72CBB6.B7A46404@summersault.com> (raw)


Hello and thanks for the Postgres team for another fine release of
Postgres. I'm working on doing some test dump/imports from Postgres 7.1
to Postgres 7.2. 

I'm using a 7.1 pg_dumpall, and a 7.2 psql to import. 

It's hanging on this error:
##########################
CREATE TABLE "mail_history" (
        "mail_id" integer DEFAULT
nextval('mail_history_mail_id_seq'::text) NOT NULL,
        "subject" character varying(200),
        "body" text,
        "group_id" integer,
        "date_created" date DEFAULT date(('current'::"timestamp" +
'00:00'::"interval")) NOT NULL,
        "n_sent" integer DEFAULT 0
);
ERROR:  Bad timestamp external representation 'current'
##################

The use of 'current' is clearly not suported as stated in the upgrade
docs. What's frustrating is that the SQL I used to create the table WAS
valid, using the standard CURRENT_DATE function, but Postgres internally
connverted this into this broken format. Here was my original create statement:
#########
create table mail_history (
        mail_id                 serial,
        subject                 varchar(200),
        body                   text,
        group_id                  integer,
        date_created               date not null default CURRENT_DATE,
        n_sent                  integer default 0
);
#######

This is from an old project. It might have started in Postgres 6.5.x and
then been imported into Postgres 7.0 and then Postgres 7.1. Is there a
way that I help coax Postgres into providing better support for this
kind of legacy data? 

   -mark



view thread (3+ messages)  latest in thread

Message-ID: <3C72CBB6.B7A46404@summersault.com>
Permalink:  ../3C72CBB6.B7A46404@summersault.com/
Also on:    postgresql.org/message-id/3C72CBB6.B7A46404@summersault.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-sql@postgresql.org
  Cc: mark@summersault.com
  Subject: Re: CURRENT_TIMESTAMP breaking with 7.1->7.2 dump/import
  In-Reply-To: <3C72CBB6.B7A46404@summersault.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox