From: Thomas F.O'Connell <tfo@sitening.com>
To: josh@agliodbs.com
Cc: PgSQL - Performance <pgsql-performance@postgresql.org>
Subject: Re: Triggers During COPY
Date: Fri, 28 Jan 2005 00:28:58 -0600
Message-ID: <0f81625232fe6b2256328804be50c7ae@sitening.com> (raw)
In-Reply-To: <200501272141.49531.josh@agliodbs.com>
References: <f2a4e35d83b33da9b5d007d276df484a@sitening.com>
<200501272141.49531.josh@agliodbs.com>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: tfo@sitening.com, josh@agliodbs.com
Subject: Re: Triggers During COPY
In-Reply-To: <0f81625232fe6b2256328804be50c7ae@sitening.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox