Re: Performance UPDATE/INSERT

a single complex insert/update sql would be always faster compared to having
a cursor and manipulating the data.
Again, it depends on what is the logic, and where actually you have the
data.

cool.
L.

On 4/11/06, MG <pgsql-general(at)carladata(dot)de> wrote:
>
> I can`t use COPY for INSERTs, because I have to manipulate each record
> indiviuell.
>
> But the problem is the UPDATEs
>
> Greetings
> Michaela
>
> ----- Original Message -----
> From: "A. Kretschmer" <andreas(dot)kretschmer(at)schollglas(dot)com>
> To: <pgsql-general(at)postgresql(dot)org>
> Sent: Tuesday, April 11, 2006 11:20 AM
> Subject: Re: [GENERAL] Performance UPDATE/INSERT
>
>
> > am 11.04.2006, um 11:08:57 +0200 mailte MG folgendes:
> >> Hello,
> >>
> >> I have about 100 000 records, which need about 30 minutes to write them
> >> with single INSERTs into PostgreSQL.
> >
> > You should better use the COPY - command for bulk inserts. This is
> > faster.
> >
> >
> > HTH, Andreas
> > --
> > Andreas Kretschmer (Kontakt: siehe Header)
> > Heynitz: 035242/47215, D1: 0160/7141639
> > GnuPG-ID 0x3FFF606C http://wwwkeys.de.pgp.net
> > === Schollglas Unternehmensgruppe ===
> >
> > ---------------------------(end of broadcast)---------------------------
> > TIP 3: Have you checked our extensive FAQ?
> >
> > http://www.postgresql.org/docs/faq
> >
> >
>
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Have you searched our list archives?
>
> http://archives.postgresql.org
>