From: | "Mark Woodward" <pgsql(at)mohawksoft(dot)com> |
---|---|
To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | "Tino Wildenhain" <tino(at)wildenhain(dot)de>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: pg_dump -- data and schema only? |
Date: | 2005-08-04 17:32:13 |
Message-ID: | 22590.24.91.171.78.1123176733.squirrel@mail.mohawksoft.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> "Mark Woodward" <pgsql(at)mohawksoft(dot)com> writes:
>> Actually, there isn't a setting to just dump the able definitions and
>> the
>> data. When you dump the schema, it includes all the tablespaces,
>> namespaces, owners, etc.
>
>> Just the table nd object declarations and data would be useful.
>
> pg_dump -t table ?
I guess what I'm not being very clear.
pg_dump -# mydb
>>
--
-- PostgreSQL database dump
--
SET client_encoding = 'SQL_ASCII';
SET check_function_bodies = false;
SET client_min_messages = warning;
SET default_with_oids = true;
--
-- Name: rtz; Type: TABLE; Schema: public; Owner: markw; Tablespace:
--
CREATE TABLE rtz (
tlid integer,
rtsq integer,
zip4l integer,
zip4r integer
);
--
-- Data for Name: rtz; Type: TABLE DATA; Schema: public; Owner: markw
--
COPY rtz (tlid, rtsq, zip4l, zip4r) FROM stdin;
208014102 0 0 0
208014098 0 0 0
207023736 0 0 0
208014112 0 0 0
207027749 0 0 0
.....
That way, it can go "easily" between various PG versions.
From | Date | Subject | |
---|---|---|---|
Next Message | Mark Woodward | 2005-08-04 17:34:01 | Re: Solving the OID-collision problem |
Previous Message | Tom Lane | 2005-08-04 17:15:28 | Re: Enhanced containment selectivity function |