pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Rod Taylor <rbt@rbt.ca>
To: Robert John Shepherd <robert@reviewer.co.uk>
Cc: pgsql-bugs@postgresql.org
Subject: Re: Bug in pg_dump
Date: 15 Nov 2002 13:51:15 -0500
Message-ID: <1037386274.14810.89.camel@jester> (raw)
In-Reply-To: <006301c289d1$a9fac7b0$f3b0313e@LAIKA>
References: <006301c289d1$a9fac7b0$f3b0313e@LAIKA>


> If you know how this problem might be fixed, list the solution below:
> ---------------------------------------------------------------------
> 
> Dump all functions and types before indexes

This causes errors in other ways.  The true solution is to have pg_dump
use a decent dependency tracking mechanism.  7.4 should hold the fix for
pg_dump, although 7.3 has the dependency tracking mechanism.

-- 
Rod Taylor <rbt@rbt.ca>



view thread (5+ messages)  latest in thread

Message-ID: <1037386274.14810.89.camel@jester>
Permalink:  ../1037386274.14810.89.camel@jester/
Also on:    postgresql.org/message-id/1037386274.14810.89.camel@jester

 · 

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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-bugs@postgresql.org
  Cc: rbt@rbt.ca, robert@reviewer.co.uk
  Subject: Re: Bug in pg_dump
  In-Reply-To: <1037386274.14810.89.camel@jester>
  References: <006301c289d1$a9fac7b0$f3b0313e@LAIKA> <1037386274.14810.89.camel@jester>

* 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