Re: Triggers During COPY
От | Thomas F.O'Connell |
---|---|
Тема | Re: Triggers During COPY |
Дата | |
Msg-id | 0f81625232fe6b2256328804be50c7ae@sitening.com обсуждение исходный текст |
Ответ на | Re: Triggers During COPY (Josh Berkus <josh@agliodbs.com>) |
Ответы |
Re: Triggers During COPY
|
Список | pgsql-performance |
I forgot to mention that I'm running 7.4.6. The README includes the caveat that pgmemcache is designed for use with 8.0. My instinct is to be hesitant using something like that in a production environment without some confidence that people have done so with good and reliable success or without more extensive testing than I'm likely to have time for primarily because support for 7.4.x is never likely to increase. Thanks for the tip, though. For the time being, it sounds like I'll probably try to implement the drop/create trigger setup during import. -tfo -- Thomas F. O'Connell Co-Founder, Information Architect Sitening, LLC http://www.sitening.com/ 110 30th Avenue North, Suite 6 Nashville, TN 37203-6320 615-260-0005 On Jan 27, 2005, at 11:41 PM, Josh Berkus wrote: > Thomas, > >> Would it be absurd to drop the triggers during import and recreate >> them >> afterward and update the counts in a summ> ary update based on >> information from the import process? > > That's what I'd do. > > Also, might I suggest storing the counts in memcached (see the > pgmemached > project on pgFoundry) rather than in a table? > > -- > --Josh > > Josh Berkus > Aglio Database Solutions > San Francisco
В списке pgsql-performance по дате отправления: