Sorry for an off topic posting...
Michal,
> Honza Novak napsal(a):
> > And my questions:
> > 1. Does someone hes similar experience? or clue what to do with it?
>
> Sure, this is considered "normal" behavior for web applications. The
> solution is to use connection pooling.
>
> > 2. What is co
>>> On Wed, Oct 24, 2007 at 7:15 AM, in message
<[EMAIL PROTECTED]>, Honza Novak
<[EMAIL PROTECTED]> wrote:
> But sometimes (i don't know exactly for what reason) some queries gets
> stuck (mostly they are inserts or updates, but realy simple) and
> postgres is unable to answer in time
In a
Hi Honza,
as Gregory wrote, let apache do the job.
The apache does queue a request if all running workers are busy.
1. Split static content.
We have an apache as frontend which serves all static content and
forwards (reverse-proxy) dynamic content to the "backends"
2. Split different types of dy
"Honza Novak" <[EMAIL PROTECTED]> writes:
> Hi all,
> i'm looking for correct or at least good enough solution for use of multiple
> apaches with single postgres database. (apaches are 2.0.x, and postgres is
> 8.1.x)
>
> At this moment i'm involved in management of a website where we have large
>
Honza Novak napsal(a):
And my questions:
1. Does someone hes similar experience? or clue what to do with it?
Sure, this is considered "normal" behavior for web applications. The
solution is to use connection pooling.
2. What is correct setup of postgresql backend serving data for many
(4+)
Hi all,
i'm looking for correct or at least good enough solution for use of
multiple apaches with single postgres database. (apaches are 2.0.x, and
postgres is 8.1.x)
At this moment i'm involved in management of a website where we have
large user load on our web servers. Apaches are set up t
