| From: | Hannu Krosing <hannu(at)tm(dot)ee> |
|---|---|
| To: | Luis Alberto Amigo Navarro <lamigo(at)atc(dot)unican(dot)es> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: question on backends |
| Date: | 2002-07-29 18:42:30 |
| Message-ID: | 1027968150.9150.7.camel@taru.tm.ee |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, 2002-07-29 at 11:32, Luis Alberto Amigo Navarro wrote:
> Hi all
> As I understand every time there is a request to postgres a new backend
> is made, and when the request is finished, even if the connection is
> already active the backend dies.
I think you have misunderstood it. A new backend is forked only when a
new connection is made, not for every transaction.
There may be some frontends that do make a new connection for each http
request or such, but most of them allow for persistent connections,
either as an option or by default.
> I wonder if is there any parameter
> that allow backends to remain beyond a transaction. Creating a new
> backend every time a transaction is made means forking the code and
> reallocating sort_memory.
------------------
Hannu
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Luis Alberto Amigo Navarro | 2002-07-29 18:50:00 | Re: question on backends |
| Previous Message | Luis Alberto Amigo Navarro | 2002-07-29 18:21:27 | Re: question on backends |