Tom Lane wrote: And here I was thinking that I'd been clear :)Naz Gassiep <[EMAIL PROTECTED]> writes:I propose that two more be added: --tables-only --constraints-onlyThis 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 But yes, you are right, what I want is "the stuff that gets loaded before data insertion" and "the stuff that goes after data insertion" Essentially, the CREATE TABLE statements are the first part as that is what is needed for data to be inserted. Everything else is the second part. |
- [HACKERS] pg_dump schema breakup Naz Gassiep
- Re: [HACKERS] pg_dump schema breakup Tom Lane
- Re: [HACKERS] pg_dump schema breakup Naz Gassiep
- Re: [HACKERS] pg_dump schema breakup Andreas Joseph Krogh
- Re: [HACKERS] pg_dump schema breakup Naz Gassiep
- Re: [HACKERS] pg_dump schema breakup Joshua D. Drake
- Re: [HACKERS] pg_dump schema br... Andrew Dunstan
- Re: [HACKERS] pg_dump schem... Naz Gassiep
- Re: [HACKERS] pg_dump schem... Alvaro Herrera
- Re: [HACKERS] pg_dump s... Andrew Dunstan
- Re: [HACKERS] pg_dump s... Tom Lane
- Re: [HACKERS] pg_dump s... Naz Gassiep