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

Re: Bug #540: pg_dump a simple table can fail if other

From: Luby Liao <liao(at)sandiego(dot)edu>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com>, liao(at)sandiego(dot)edu, pgsql-bugs(at)postgresql(dot)org
Subject: Re: Bug #540: pg_dump a simple table can fail if other
Date: 2001-12-17 03:18:55
Message-ID: 15389.25631.302003.192144@holycow.acusd.edu (view raw or flat)
Thread:
Lists: pgsql-bugs
Tom and Stephan, thank you so much for the prompt reply.  cheers, Luby

 > Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com> writes:
 > > We're going to need some additional information for this to be a
 > > complete report.
 > 
 > It doesn't really require investigation.  pg_dump pulls the entire
 > schema before deciding what parts of it need to be dumped; therefore
 > schema-level problems are likely to cause pg_dump to error out even
 > if that part of the schema theoretically didn't need to be examined.
 > 
 > I am disinclined to invest any effort in changing this, in part because
 > I doubt it could be changed without making it impossible to do other
 > things that we want to do in the near future (cf. nearby discussion
 > about dumping sequences associated with the target table).
 > 
 > 			regards, tom lane

In response to

pgsql-bugs by date

Next:From: JustinDate: 2001-12-17 04:42:58
Subject: Re: Unable to compare _bpchar for similarity in WHERE-clause (MINOR A NNOYANCE)
Previous:From: Tom LaneDate: 2001-12-17 01:31:35
Subject: Re: Bug #540: pg_dump a simple table can fail if other

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