"Get thee to a connection pooler ASAP."
We've got systems where we establish ~1K connections, but that's on
UNIX, where the handling of large systems is *WAY* more mature than
Windows.
Any time those kinds of quantities of connections appear necessary, it
seems highly preferable to be using conne
> > I need to run about 1000 PostgreSQL connections on a server that I
can
> > use about 4 GB of the total 16 GB of total RAM. It seems that each
> > session creates a process that uses about 15 MB of RAM just for
> > connecting so I'm running out of RAM rather quickly.
>
> I think you're being b
"Roberts, Jon" <[EMAIL PROTECTED]> writes:
> I need to run about 1000 PostgreSQL connections on a server that I can
> use about 4 GB of the total 16 GB of total RAM. It seems that each
> session creates a process that uses about 15 MB of RAM just for
> connecting so I'm running out of RAM rather
Roberts, Jon wrote:
I need to run about 1000 PostgreSQL connections on a server that I can
use about 4 GB of the total 16 GB of total RAM. It seems that each
session creates a process that uses about 15 MB of RAM just for
connecting so I’m running out of RAM rather quickly.
I have these n
I need to run about 1000 PostgreSQL connections on a server that I can
use about 4 GB of the total 16 GB of total RAM. It seems that each
session creates a process that uses about 15 MB of RAM just for
connecting so I'm running out of RAM rather quickly.
I have these non-default settings:
sha
