Re: pg_dump bug in 7.4

From: Robert Creager <Robert_Creager(at)LogicalChaos(dot)org>
To: Bruno Wolff III <bruno(at)wolff(dot)to>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: pg_dump bug in 7.4
Date: 2003-10-04 17:51:28
Message-ID: 20031004115128.05433828.Robert_Creager@LogicalChaos.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

When grilled further on (Sat, 4 Oct 2003 12:50:27 -0500),
Bruno Wolff III <bruno(at)wolff(dot)to> confessed:

> The following is still a problem in current cvs (as of 2 hours ago).
> Normally I wouldn't bug people about this again this soon, but with talk of
> a release candidate next week I wanted to make sure that it wasn't forgotten.
>

I just hit the same problem (with 7.4b4).

CREATE TABLE processing (
"index" integer NOT NULL,
"time" timestamp with time zone DEFAULT now() NOT NULL,
archname_index integer,
CONSTRAINT archname_index CHECK NULL::boolean
);

Cheers,
Rob

--
11:49:30 up 64 days, 4:19, 4 users, load average: 4.37, 3.83, 3.53

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2003-10-04 17:51:38 Re: count(*) slow on large tables
Previous Message Bruno Wolff III 2003-10-04 17:50:27 Re: pg_dump bug in 7.4