Continual uptime while loading data ... COPY vs INSERTS within a transaction.
От
Benjamin Arai
Тема
Continual uptime while loading data ... COPY vs INSERTS within a
transaction.
Дата
Msg-id
47AE3779.6010101@benjaminarai.com
Список
Дерево обсуждения
Continual uptime while loading data ... COPY vs INSERTS within a
transaction. Benjamin Arai <me@benjaminarai.com>
Re: Continual uptime while loading data ... COPY vs INSERTS within a transaction. Tom Lane <tgl@sss.pgh.pa.us>
Re: Continual uptime while loading data ... COPY vs
INSERTS within a transaction. Gerald Timothy Quimpo <bopolissimus.lists@gmail.com>
Re: Continual uptime while loading data ... COPY vs INSERTS within a transaction. "Christopher Browne" <cbbrowne@gmail.com>
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 10000 inserts). This process works well allowing both end users to access the data as well as loading reasonably quickly. 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? Benjamin
В списке pgsql-general по дате отправления
От: ptjm@interlog.com (Patrick TJ McPhee)
Дата:
Сообщение: Re: [OT] "advanced" database design (long)