From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
---|---|
To: | FattahRozzaq <ssoorruu(at)gmail(dot)com> |
Cc: | PostgreSQL mailing lists <pgsql-performance(at)postgresql(dot)org> |
Subject: | Re: PostgreSQL limitation |
Date: | 2015-11-02 12:12:21 |
Message-ID: | CAB7nPqSvjF7kssjmb+roobGRD71QWQmj8n0RuMRR9Q9b8mX1Mg@mail.gmail.com |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
On Mon, Nov 2, 2015 at 7:52 PM, FattahRozzaq <ssoorruu(at)gmail(dot)com> wrote:
> If I install the PostgreSQL on Linux (Debian),
> How much the limit of max_connections that PostgreSQL can take?
> How much the limit of max_prepared_transactions that PostgreSQL can take?
Per definition, those parameters have a max value of 2^23-1. For a
Postgres instance, a couple of hundred connections is already a lot,
and you'd want not really much more than the maximum number of
connections for max_prepared_transactions.
> How much the limit of max_files_per_process that PostgreSQL can take?
And this one has a maximum limit of 2^31-1. This can be helpful on
some platforms where kernel allows a process to open more files than
it can, like FreeBSD.
--
Michael
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2015-11-02 14:45:05 | Re: Slow query in trigger function |
Previous Message | FattahRozzaq | 2015-11-02 10:52:15 | PostgreSQL limitation |