Re: pg_dump schema breakup

From: Naz Gassiep <naz(at)mira(dot)net>
To: Andreas Joseph Krogh <andreak(at)officenet(dot)no>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: pg_dump schema breakup
Date: 2006-08-18 17:33:03
Message-ID: 44E5F9CF.1080407@mira.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-15"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Andreas Joseph Krogh wrote:
<blockquote cite="mid200608181857(dot)25252(dot)andreak(at)officenet(dot)no"
type="cite">
<pre wrap="">On Friday 18 August 2006 18:52, Tom Lane wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Naz Gassiep <a class="moz-txt-link-rfc2396E" href="mailto:naz(at)mira(dot)net">&lt;naz(at)mira(dot)net&gt;</a> writes:
</pre>
<blockquote type="cite">
<pre wrap="">I propose that two more be added:
--tables-only
--constraints-only
</pre>
</blockquote>
<pre wrap="">This doesn't seem well-defined at all. There are many objects in a
database that are definitely neither tables nor constraints, and it's
not very clear what things should be considered constraints either.

I think what you may really be after is "the stuff that should be loaded
before inserting data" and "the stuff that should be loaded after", but
the above are poor names for these concepts.
</pre>
</blockquote>
<pre wrap=""><!---->
But it certainly would be nice to be able to dump all that "stuff":-)</pre>
</blockquote>
Yea, I've been told that this would not be a high demand feature. So do
I have a second vote? ;-)<br>
</body>
</html>

Attachment Content-Type Size
unknown_filename text/html 1.3 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Joshua D. Drake 2006-08-18 17:39:38 Re: pg_dump schema breakup
Previous Message David Fetter 2006-08-18 17:16:40 Re: [PATCHES] selecting large result sets in psql using