pg.ddx.io pgsql-admin@postgresql.org mailing list archive
help / color / mirror / Atom feedPerformance question: Restore + INDEX
3+ messages / 3 participants
[nested] [flat]
* Performance question: Restore + INDEX
@ 2005-09-26 00:30 Aldor <an@mediaroot.de>
2005-09-26 01:19 ` Re: Performance question: Restore + INDEX Michael Fuhr <mike@fuhr.org>
2005-09-26 03:43 ` Re: Performance question: Restore + INDEX Chris Browne <cbbrowne@acm.org>
0 siblings, 2 replies; 3+ messages in thread
From: Aldor @ 2005-09-26 00:30 UTC (permalink / raw)
To: pgsql-admin
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
^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: Performance question: Restore + INDEX
2005-09-26 00:30 Performance question: Restore + INDEX Aldor <an@mediaroot.de>
@ 2005-09-26 01:19 ` Michael Fuhr <mike@fuhr.org>
1 sibling, 0 replies; 3+ messages in thread
From: Michael Fuhr @ 2005-09-26 01:19 UTC (permalink / raw)
To: Aldor <an@mediaroot.de>; +Cc: pgsql-admin
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
^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: Performance question: Restore + INDEX
2005-09-26 00:30 Performance question: Restore + INDEX Aldor <an@mediaroot.de>
@ 2005-09-26 03:43 ` Chris Browne <cbbrowne@acm.org>
1 sibling, 0 replies; 3+ messages in thread
From: Chris Browne @ 2005-09-26 03:43 UTC (permalink / raw)
To: pgsql-admin
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
^ permalink raw reply [nested|flat] 3+ messages in thread
end of thread, other threads:[~2005-09-26 03:43 UTC | newest]
Thread overview: 3+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2005-09-26 00:30 Performance question: Restore + INDEX Aldor <an@mediaroot.de>
2005-09-26 01:19 ` Michael Fuhr <mike@fuhr.org>
2005-09-26 03:43 ` Chris Browne <cbbrowne@acm.org>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox