On Wed, Apr 21, 2004 at 09:12:27PM -0400, Jon Pastore wrote:
> This perl script is designed to handle payment posting for an application we
> developed. It runs fine on our development server which is running apache
> 1.3.27 on ES 2.1
>
> on the production server the script hangs and we see the
On Tue, Apr 20, 2004 at 01:30:59PM -0300, Marc G. Fournier wrote:
> Also check to make sure that you don't have autolearn disabled ... you
> would have had to do it manually, as it is enabled by default, but, for
> instance, if you are a user on a system, the site-wide may be set to
> disable autol
On Mon, Apr 19, 2004 at 09:19:05PM -0700, Joe Conway wrote:
> Marc G. Fournier wrote:
> >Huh? I just use Spamassassin myself, with Razor/Pyzor/DCC and Bayes all
> >enabled ...
>
> I use exactly the same setup. But recently I've noticed that the
> spammers are getting smarter -- I think 20% of it
Not reading the newsgroup, I missed the original. But here's my two
cents.
First, do not use Microsoft products on a web server unless you want to
spend all your time applying patches and cleaning up the results of your
server being used as a warez site. The initial setup might be easy, but
the
On Thu, Mar 04, 2004 at 10:50:50AM -0500, Tom Lane wrote:
> If I understood the requirements correctly, it might be sufficient to
> put a unique index on (id1,id2). If two transactions simultaneously try
> to insert for the same id1, one would get a duplicate-index-entry
> failure, and it would ha
On Wed, Mar 03, 2004 at 06:45:56AM +0100, Paulovi?? Michal wrote:
> Yes I know,
>
> But how you do this at PgSQL
You have to lock the table exclusively, get the max value for your
particular "id1", increment it, insert the row, and commit:
begin;
lock table test in exclusive mode;
insert int
> >The original subquery looked like:
> >select distinct e.ItemID from LogEvent e left outer join Item i
> >on e.ItemID = i.ItemID where e.EventType != 'i' and i.ItemID is null
Please, before continuing this thread, read my post below. What you're
all getting around to, albeit painfully, is that
On Fri, Feb 27, 2004 at 12:06:58PM -, Simon Windsor wrote:
> Hi
>
> I have moved an application from MySQL to PgSQL, and after the making
> changes I thought all was ok.
>
> However, I have just realised that
>
> Where A = 'STRING'
>
> Is not the same as
>
> Where A ='String'
This is sta
On Thu, Feb 26, 2004 at 06:26:19PM -0800, [EMAIL PROTECTED] wrote:
> I'm using postgresl 7.3.2 and have a query that executes very slowly.
>
> There are 2 tables: Item and LogEvent. ItemID (an int4) is the
> primary key
> of Item, and is also a field in LogEvent. Some ItemIDs in LogEvent do
> not
