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

Re: [BUGS] Re: [HACKERS] pg_dump error

From: Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us>
To: ccb(at)pubweb(dot)net (Charles Bennett)
Cc: sferac(at)bo(dot)nettuno(dot)it, pgsql-hackers(at)postgreSQL(dot)org, pgsql-bugs(at)postgreSQL(dot)org
Subject: Re: [BUGS] Re: [HACKERS] pg_dump error
Date: 1998-06-17 22:54:45
Message-ID: 199806172254.SAA06193@candle.pha.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackers
> 
> 
> I (thought I) forwarded fixes for the pg_dump constraint syntax
> bug to this list a couple of weeks ago.  I added a -c (compatible)
> switch to pg_dump to force it to dump constraints in a syntax that
> pgsql can understand.
> 
> Here's another copy of the diffs (against 6.3.2).
> 

I just applied this patch a few days ago.  I e-mailed you asking why
there is an option for this behavour.  Seems like it should always be
on.

Please let me know.

-- 
Bruce Momjian                          |  830 Blythe Avenue
maillist(at)candle(dot)pha(dot)pa(dot)us              |  Drexel Hill, Pennsylvania 19026
  +  If your life is a hard drive,     |  (610) 353-9879(w)
  +  Christ can be your backup.        |  (610) 853-3000(h)

In response to

pgsql-hackers by date

Next:From: Aleksey DashevskyDate: 1998-06-18 09:56:13
Subject: Non-functional update, only first update is performed
Previous:From: Bruce MomjianDate: 1998-06-17 22:43:25
Subject: Re: AW: [HACKERS] using a btree index in order by clause?

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