Re: Trouble incrementing a column

Поиск
Список
Период
Сортировка
Искать
От
Jeff Janes
Тема
Re: Trouble incrementing a column
Дата
Msg-id
CAMkU=1w61H6siZF0f+UTSLp_e8=sM7SNT_aFsk6_8kipRsvQGw@mail.gmail.com
Ответ на
Список
Дерево обсуждения
Trouble incrementing a column Blake McBride <blake1024@gmail.com>
Re: Trouble incrementing a column Tom Lane <tgl@sss.pgh.pa.us>
Re: Trouble incrementing a column Jeff Janes <jeff.janes@gmail.com>
Re: Trouble incrementing a column Tom Lane <tgl@sss.pgh.pa.us>
Re: Trouble incrementing a column Ron <ronljohnsonjr@gmail.com>
On Sat, Nov 23, 2019 at 4:47 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
 
Note that you pay a fairly substantial performance penalty for deferring
the check, which is why it isn't the default, even though the SQL spec
says it ought to be.

Do you know what the worst case scenario is for the performance of deferring the check to the end of the statement (with deferred initially immediate)?  Upon testing, I get a penalty of 2 to 5%, which seems pretty small, but I might not be testing the most adverse situation.  See attached.

The main "cost" that prevents from using DII routinely is that they can't receive foreign key constraints.  

Cheers,

Jeff

В списке pgsql-general по дате отправления
От: Tom Lane
Дата:
От: Tom Lane
Дата:
FAQ