Re: [GENERAL] slow inserts and updates on large tables

1999-02-17 Thread Herouth Maoz
At 16:47 +0200 on 17/2/99, Jim Mercer wrote: > i will test this with my insertama program, but i see some problems with >this. > > firstly, it assumes that all of your applications programs are updated each > time you modify the structure of the table. This is true. That's the sacrifice you get

Re: [GENERAL] slow inserts and updates on large tables

1999-02-17 Thread Jim Mercer
> At 16:10 +0200 on 17/2/99, Jim Mercer wrote: > You probably didn't understand me. If you convert it to tab delimited text > and then use COPY table_name FROM filename/stdin instead of INSERT, it will > be much faster, because you don't have to do the parsing and planning on > each line, but only

Re: [GENERAL] slow inserts and updates on large tables

1999-02-17 Thread Herouth Maoz
At 16:10 +0200 on 17/2/99, Jim Mercer wrote: > > > 3) Back to the issue of INSERTS - copies are faster. If you can transform > >the data into tab-delimited format as required by COPY, you save a lot > >of time on parsing, planning etc. > > this sorta defeats the purpose of putting the da

Re: [GENERAL] slow inserts and updates on large tables

1999-02-17 Thread Jim Mercer
> How about -o -F ? the startup script is: [ -x /usr/local/pgsql/bin/postmaster ] && { su -l pgsql -c 'exec /usr/local/pgsql/bin/postmaster -i -S -o -F -d 3 \ -D/usr/local/pgsql/data' >> /usr/local/pgsql/errlog 2>&1 echo -n ' pgsql' } -- [ Jim MercerReptilian Research

Re: [GENERAL] slow inserts and updates on large tables

1999-02-17 Thread Jim Mercer
> > if anyone has any pointers as to why this is so slow, lemme know. > > Have you checked the usual stuff: > > 1) Each insert and update creates its own transaction. That is, an >insert is in fact: > >BEGIN TRANSACTION; >INSERT...; >COMMIT; > >So, to make things faster you