Re: pg_dump schema breakup - Mailing list pgsql-hackers

From Naz Gassiep
Subject Re: pg_dump schema breakup
Date
Msg-id 44E5F2A2.2020709@mira.net
Whole thread Raw
In response to Re: pg_dump schema breakup  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
<br /> Tom Lane wrote: <blockquote cite="mid21511.1155919931@sss.pgh.pa.us" type="cite"><pre wrap="">Naz Gassiep <a
class="moz-txt-link-rfc2396E"href="mailto:naz@mira.net"><naz@mira.net></a> writes: </pre><blockquote
type="cite"><prewrap="">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.
        regards, tom lane</pre></blockquote> And here I was thinking that I'd been clear :)<br /><br /> But yes, you
areright, what I want is "the stuff that gets loaded before data insertion" and "the stuff that goes after data
insertion"<br/><br /> Essentially, the CREATE TABLE statements are the first part as that is what is needed for data to
beinserted. Everything else is the second part.  

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: pg_dump schema breakup
Next
From: David Fetter
Date:
Subject: Re: [PATCHES] selecting large result sets in psql using