Re: Proposal: Change of pg_trigger.tg_enabled and adding

Поиск
Список
Период
Сортировка
От Jim Nasby
Тема Re: Proposal: Change of pg_trigger.tg_enabled and adding
Дата
Msg-id D8A6DB1C-6B83-4A7F-BA6F-B7C94A3CA460@decibel.org
обсуждение исходный текст
Ответ на Re: Proposal: Change of pg_trigger.tg_enabled and adding  (Markus Schiltknecht <markus@bluegap.ch>)
Ответы Re: Proposal: Change of pg_trigger.tg_enabled and adding  (Jan Wieck <JanWieck@Yahoo.com>)
Re: Proposal: Change of pg_trigger.tg_enabled and adding  (Markus Schiltknecht <markus@bluegap.ch>)
Список pgsql-hackers
On Jan 26, 2007, at 5:13 AM, Markus Schiltknecht wrote:
> In Postgres-R, I mostly use the terms 'local' and 'remote'.

Note that those terms only make sense if you limit yourself to  
thinking the master is pushing data out to the slave...

I think it'd make the most sense if the name reflected whether the  
trigger should be fired by a replication process or not; that way it  
doesn't really matter if it's a master or a slave... if the data in  
the table is being modified by a replication process then you don't  
fire the trigger/rule, according to the setting. But maybe there is  
some need to discern between origin and target...

Also, if enums will be in 8.3, perhaps they can be used instead of  
"char"?
--
Jim Nasby                                            jim@nasby.net
EnterpriseDB      http://enterprisedb.com      512.569.9461 (cell)




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

Предыдущее
От: Jim Nasby
Дата:
Сообщение: Re: BUG #2917: spi_prepare doesn't accept typename aliases
Следующее
От: Jim Nasby
Дата:
Сообщение: Re: Proposal: Change of pg_trigger.tg_enabled and adding pg_rewrite.ev_enabled