Search Postgresql Archives

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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Benjamin Arai <me@xxxxxxxxxxxxxxxx> 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 an exclusive lock? Second, is 
> there a better way to load data?

No, and no.  Use COPY.

			regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
       choose an index scan if your joining column's datatypes do not
       match

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux