Message-ID: <55738.63.227.74.41.1097975404.squirrel@63.227.74.41>
In-Reply-To: <20041017004929.GB19149@commandprompt.com>
References: <56362.63.227.74.41.1097813923.squirrel@63.227.74.41>
	<87hdow4ld1.fsf@stark.xeocode.com>
	<64883.63.227.74.41.1097846113.squirrel@63.227.74.41>
	<20041017004929.GB19149@commandprompt.com>
Date: Sat, 16 Oct 2004 20:09:42 -0500 (CDT)
Subject: Re: Inserting into table only if the row does not already
From: "C. Bensend" <benny@bennyvision.com>
To: pgsql-sql@postgresql.org
User-Agent: SquirrelMail/1.4.3a
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Importance: Normal


> Even cron'd scripts can run amok. Lock files are great as a CYA
> measure even if you're relatively certain there will be no opportunity
> for one copy to step on the next.

Yes, you are absolutely correct, of course.  :)

I should be more specific - I'm working on a personal project, and I'm
not going to worry about that right now.  The risk of a cron gone wild
is acceptable to me at this moment.

Right now my priority is getting data flowing into the database instead
of piling up on the host like it is.  :)

Thanks much!

Benny


-- 
"Even if a man chops off your hand with a sword, you still have two nice,
sharp bones to stick in his eyes."
                                                      -- .sig on Slashdot