Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id E4A23475AD4 for ; Sat, 25 Jan 2003 13:57:38 -0500 (EST) Received: from lakemtao03.cox.net (lakemtao03.cox.net [68.1.17.242]) by postgresql.org (Postfix) with ESMTP id 2BA3C474E61 for ; Sat, 25 Jan 2003 13:57:38 -0500 (EST) Received: from [192.168.1.1] ([68.11.66.83]) by lakemtao03.cox.net (InterMail vM.5.01.04.05 201-253-122-122-105-20011231) with ESMTP id <20030125185735.QHYY8666.lakemtao03.cox.net@[192.168.1.1]> for ; Sat, 25 Jan 2003 13:57:35 -0500 Subject: LOCK TABLE & speeding up mass data loads From: Ron Johnson To: PgSQL Performance ML Content-Type: text/plain Organization: Message-Id: <1043521053.818.32.camel@haggis> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.1 Date: 25 Jan 2003 12:57:33 -0600 Content-Transfer-Encoding: 7bit X-Virus-Scanned: by AMaViS new-20020517 X-Archive-Number: 200301/331 X-Sequence-Number: 978 Hi, Would LOCK TABLE ACCESS EXCLUSIVE MODE speed things up, when I have a script that loads data by setting transactions, and then committing works after every few thousand INSERTs? Thanks, Ron -- +---------------------------------------------------------------+ | Ron Johnson, Jr. mailto:ron.l.johnson@cox.net | | Jefferson, LA USA http://members.cox.net/ron.l.johnson | | | | "Fear the Penguin!!" | +---------------------------------------------------------------+