Re: Concurrent Inserts

Поиск
Список
Период
Сортировка
От Albe Laurenz
Тема Re: Concurrent Inserts
Дата
Msg-id A737B7A37273E048B164557ADEF4A58B3658E33B@ntex2010i.host.magwien.gv.at
обсуждение исходный текст
Ответ на Re: Concurrent Inserts  (sri harsha <sriharsha9992@gmail.com>)
Список pgsql-general
sri harsha wrote:
>>>    Is there any way to stop concurrent inserts to happen on a single table ??

>> If you really want that, it is easy with table locks.

>     Actually i am using a FDW , in which the data is written into a single file. So when i do
> concurrent inserts , the data is written into the file simultaneously and this is causing a data
> corruption . Is TABLE LOCK the only option available ??

In that case I would say that the FDW is broken.

If concurrent modifications corrupt the data, the FDW should make sure that not more
than one modification to the same data can happen at the same time, perhaps by using
PostgreSQL advisory locks or IPC mechanisms.

Yours,
Laurenz Albe

В списке pgsql-general по дате отправления:

Предыдущее
От: sri harsha
Дата:
Сообщение: Re: Concurrent Inserts
Следующее
От: Spiros Ioannou
Дата:
Сообщение: Re: partitioning query planner almost always scans all tables