| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Cc: | Markus Wanner <markus(at)bluegap(dot)ch>, Robert Haas <robertmhaas(at)gmail(dot)com> |
| Subject: | Re: changing MyDatabaseId |
| Date: | 2010-11-17 11:09:16 |
| Message-ID: | 201011171209.17097.andres@anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wednesday 17 November 2010 11:58:33 Markus Wanner wrote:
> Andreas,
>
> On 11/17/2010 11:38 AM, Andres Freund wrote:
> > Well, one could optimize most of the resetting away if the the old
> > MyDatabaseId and the new one are the same - an optimization which is
> > hardly possible with forking new backends.
> Uh? Why not simply re-use the same backend, then? Or do you think of
> re-connecting to the same database as a way to reset your connection?
I am thinking of a connection-pooler like setup. Quite often your main-load
goes towards a single database - in that situation you don't have to reset the
database id most of the time.
Andres
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Markus Wanner | 2010-11-17 11:32:43 | Re: changing MyDatabaseId |
| Previous Message | Markus Wanner | 2010-11-17 10:58:33 | Re: changing MyDatabaseId |