duplicates rejected by index reports PGSQL_FATAL_ERROR

Поиск
Список
Период
Сортировка
От tj
Тема duplicates rejected by index reports PGSQL_FATAL_ERROR
Дата
Msg-id 7p0ob.75320$ZH4.55826@twister.socal.rr.com
обсуждение исходный текст
Ответы Re: duplicates rejected by index reports PGSQL_FATAL_ERROR
Список pgsql-general
v7.2.2

When an insert fails because its in violation of an index (duplicate), I get
a return code 7 (PGSQL_FATAL_ERROR) in my php 4.2.3 interface.

Its not really a fatal error, is it?  Shouldn't it be reported as a
NONFATAL_ERROR ?

I have a "dumb" synchronizing task, that attempts to import a daily
cumulative batch of records, relying on a specific table index to reject
the records that were successfully imported from previous runs.  The "index
rejection" method takes only 25 seconds for my batch of 30,000 records,
while the "select to find if non-existing then perform the insert" takes 25
minutes.  Is there a better way?

--
TJ

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

Предыдущее
От: "Daniele Varrazzo"
Дата:
Сообщение: Altering columns order
Следующее
От: Åsmund Kveim Lie
Дата:
Сообщение: Cartesian product bug?