Re: Porting MSSQL to PGSQL (Was: [OT] MySQL is bad, but THIS bad?)

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: Porting MSSQL to PGSQL (Was: [OT] MySQL is bad, but THIS bad?)
Дата
Msg-id 16132.1148341666@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Re: Porting MSSQL to PGSQL (Was: [OT] MySQL is bad, but  (Andrew Dunstan <andrew@dunslane.net>)
Ответы Re: Porting MSSQL to PGSQL -- triggers  (Mischa Sandberg <mischa@ca.sophos.com>)
Список pgsql-hackers
Andrew Dunstan <andrew@dunslane.net> writes:
> How expensive is this going to be, especially for huge numbers of rows? 

Certainly cheaper than firing a per-row trigger.

> Would it be done for all queries, or just those with a per statement 
> trigger, or only when explicitly requested?

Just when there's a per-statement AFTER trigger, I would think.  One of
the tricky parts is to minimize overhead if the trigger never actually
asks for access to the rows.  However, if all we do during the statement
is build a possibly-lossy bitmap, I don't think the overhead will be
bad.

It might be interesting to think about reimplementing the RI triggers
as per-statement, too ...
        regards, tom lane


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

Предыдущее
От: Andrew Dunstan
Дата:
Сообщение: Re: Porting MSSQL to PGSQL (Was: [OT] MySQL is bad, but
Следующее
От: Bruno Wolff III
Дата:
Сообщение: Re: group by points