Thread: Performance question: Restore + INDEX

Hi,

I'm curious how other people do it:

What is faster?

1. CREATE TABLE
2. restore data
3. CREATE INDEX

or

1. CREATE TABLE
2. CREATE INDEX
3. restore data

Thanks,

Aldor

On Mon, Sep 26, 2005 at 01:30:53AM +0100, Aldor wrote:
> What is faster?
>
> 1. CREATE TABLE
> 2. restore data
> 3. CREATE INDEX
>
> or
>
> 1. CREATE TABLE
> 2. CREATE INDEX
> 3. restore data

See "Populating a Database" in the "Performance Tips" chapter of
the documentation:

http://www.postgresql.org/docs/8.0/interactive/populate.html

But instead of taking somebody's word for it, you could simply try
it both ways and see which is faster for yourself.

--
Michael Fuhr

an@mediaroot.de (Aldor) writes:
> I'm curious how other people do it:
>
> What is faster?
>
> 1. CREATE TABLE
> 2. restore data
> 3. CREATE INDEX
>
> or
>
> 1. CREATE TABLE
> 2. CREATE INDEX
> 3. restore data

Creating the index AFTER loading the data is definitely faster.  But
by all means do your own tests; it's pretty easy to do so and satisfy
yourself...
--
(format nil "~S@~S" "cbbrowne" "ntlug.org")
http://cbbrowne.com/info/languages.html
"It worked about as well as sticking a blender in the middle of a lime
plantation and hoping they'll make margaritas out of themselves."
-- Frederick J. Polsky v1.0