Re: [GENERAL] Continual uptime while loading data ... COPY vs INSERTS within a transaction.

2008-02-11 Thread Gerald Timothy Quimpo
On Sat, 2008-02-09 at 19:27 -0500, Tom Lane wrote: > Benjamin Arai <[EMAIL PROTECTED]> writes: > > We are thinking of modifying our system to use COPY to replace these > > large INSERT transactions but we are concerned that it will greatly > > impact the user experience (i.e., exclusively lock t

Re: [GENERAL] Continual uptime while loading data ... COPY vs INSERTS within a transaction.

2008-02-09 Thread Tom Lane
Benjamin Arai <[EMAIL PROTECTED]> writes: > We are thinking of modifying our system to use COPY to replace these > large INSERT transactions but we are concerned that it will greatly > impact the user experience (i.e., exclusively lock the table during the > copy process). First, does COPY grab

Re: [GENERAL] Continual uptime while loading data ... COPY vs INSERTS within a transaction.

2008-02-09 Thread Christopher Browne
On Feb 9, 2008 6:30 PM, Benjamin Arai <[EMAIL PROTECTED]> wrote: > Hello, > > We are running a system which requires continual uptime while loading > data. Currently one particular table receives a large number of inserts > per commit (about 1 inserts). This process works well allowing both >

[GENERAL] Continual uptime while loading data ... COPY vs INSERTS within a transaction.

2008-02-09 Thread Benjamin Arai
Hello, We are running a system which requires continual uptime while loading data. Currently one particular table receives a large number of inserts per commit (about 1 inserts). This process works well allowing both end users to access the data as well as loading reasonably quickly. W