Re: Re: AW: Plans for solving the VACUUM problem - Mailing list pgsql-hackers

From Denis Perchine
Subject Re: Re: AW: Plans for solving the VACUUM problem
Date
Msg-id 20010522071641.9F99A1C49B@mx.webmailstation.com
Whole thread Raw
In response to Re: AW: Plans for solving the VACUUM problem  (Lincoln Yeoh <lyeoh@pop.jaring.my>)
List pgsql-hackers
> >    As  a  rule  of  thumb,  online  applications  that hold open
> >    transactions during user interaction  are  considered  to  be
> >    Broken  By  Design  (tm).   So I'd slap the programmer/design
> >    team with - let's use the server box since it doesn't contain
> >    anything useful.
>
> Many web applications use persistent database connections for performance
> reasons.

Persistent connection is not the same as an OPEN transaction BTW.

> I suppose it's unlikely for webapps to update a row and then sit and wait a
> long time for a hit, so it shouldn't affect most of them.
>
> However if long running transactions are to be aborted automatically, it
> could possibly cause problems with some apps out there.
>
> Worse if long running transactions are _disconnected_ (not just aborted).

-- 
Sincerely Yours,
Denis Perchine

----------------------------------
E-Mail: dyp@perchine.com
HomePage: http://www.perchine.com/dyp/
FidoNet: 2:5000/120.5
----------------------------------


pgsql-hackers by date:

Previous
From: Zeugswetter Andreas SB
Date:
Subject: AW: Is stats update during COPY IN really a good idea?
Next
From: Zeugswetter Andreas SB
Date:
Subject: AW: AW: Plans for solving the VACUUM problem