From: | Guido Barosio <gbarosio(at)gmail(dot)com> |
---|---|
To: | Colton A Smith <smith(at)cs(dot)utk(dot)edu> |
Cc: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: COPY and partitioning |
Date: | 2005-11-19 00:29:54 |
Message-ID: | f7f6b4c70511181629uaddf3d4t237c360a0b5019d6@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Thinking about dumping the schema, rewriting that structure with your
partitioning needs, and after copy the data.
Why not?
Just 2 cents, never done it.
to dump a schema:
pg_dump -s dbname > dbname.schema
Then just restore the data, it should work I guess.
Best regards,
Guido
On 11/17/05, Colton A Smith <smith(at)cs(dot)utk(dot)edu> wrote:
>
> Hi
>
> I understand v8.1 implements table partitioning. Very exciting!
>
> I have a big table (30 G) that is a real headache. I'd like to
> partition it. My plan is the following: (1) use pg_dump -t to
> dump the data; (2) create a partitioning schema with check constraints;
> and (3) repopulate using the COPY utility.
>
> My question: does the COPY utility consult check constraints
> before populating tables?
>
> Thanks as always.
>
> ---------------------------(end of broadcast)---------------------------
> TIP 6: explain analyze is your friend
>
--
"Adopting the position that you are smarter than an automatic
optimization algorithm is generally a good way to achieve less
performance, not more" - Tom Lane.
From | Date | Subject | |
---|---|---|---|
Next Message | vinod.sadanandan | 2005-11-19 11:06:04 | Batch Files |
Previous Message | John Jensen | 2005-11-19 00:15:46 | Re: Server Hardware Configuration |