| From: | "Dann Corbit" <DCorbit(at)connx(dot)com> |
|---|---|
| To: | "Jim C(dot) Nasby" <decibel(at)decibel(dot)org> |
| Cc: | "Ben-Nes Yonatan" <da(at)canaan(dot)co(dot)il>, <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Populating huge tables each day |
| Date: | 2005-06-27 20:05:42 |
| Message-ID: | D425483C2C5C9F49B5B7A41F8944154757CE9E@postal.corporate.connx.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
> -----Original Message-----
> From: Jim C. Nasby [mailto:decibel(at)decibel(dot)org]
> Sent: Monday, June 27, 2005 12:58 PM
> To: Dann Corbit
> Cc: Ben-Nes Yonatan; pgsql-general(at)postgresql(dot)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?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ben-Nes Yonatan | 2005-06-27 20:13:10 | Populating huge tables each day |
| Previous Message | Jim C. Nasby | 2005-06-27 19:58:00 | Re: Populating huge tables each day |