Re: Populating huge tables each day - Mailing list pgsql-general

From Dann Corbit
Subject Re: Populating huge tables each day
Date
Msg-id D425483C2C5C9F49B5B7A41F8944154757CE9E@postal.corporate.connx.com
Whole thread Raw
In response to Populating huge tables each day  (Ben-Nes Yonatan <da@canaan.co.il>)
Responses Re: Populating huge tables each day  ("Jim C. Nasby" <decibel@decibel.org>)
List pgsql-general
> -----Original Message-----
> From: Jim C. Nasby [mailto:decibel@decibel.org]
> Sent: Monday, June 27, 2005 12:58 PM
> To: Dann Corbit
> Cc: Ben-Nes Yonatan; pgsql-general@postgresql.org
> Subject: Re: [GENERAL] Populating huge tables each day
>
> On Mon, Jun 27, 2005 at 12:43:57PM -0700, Dann Corbit wrote:
> > I see a lot of problems with this idea.
> >
> > You mention that the database is supposed to be available 24x7.
> > While you are loading, the database table receiving data will not be
> > available.  Therefore, you will have to have one server online (with
>
> Why do you think that's the case?

He's doing a bulk load.  I assume he will have to truncate the table and
load it with the copy command.

Is there an alternative I do not know of that is equally fast?

pgsql-general by date:

Previous
From: "Jim C. Nasby"
Date:
Subject: Re: Populating huge tables each day
Next
From: John Browne
Date:
Subject: Re: Finding points within 50 miles