| From: | Greg Stark <gsstark(at)mit(dot)edu> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Markus Wanner <markus(at)bluegap(dot)ch>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: changing MyDatabaseId |
| Date: | 2010-11-17 19:11:52 |
| Message-ID: | AANLkTikx_Vj9O4d2iubO_wXso=-3vo87SyQ_bJWNMNd1@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Nov 17, 2010 at 6:33 PM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> I think you're missing the point. If we switch databases, all cached
> relations and plans have to be flushed anyway. We're talking about
> what might NOT need to be flushed on switching databases.
Oh sorry, yes, I missed that point.
I will mention that your point about TCP connection establishment
latency is real. TCP connection establishment adds several
milliseconds of latency (for low latency connections -- obviously it's
much much worse for long-haul connections) and then the congestion
control slow start adds more if there's a significant amount of data
to transfer.
--
greg
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2010-11-17 19:16:06 | Re: unlogged tables |
| Previous Message | Magnus Hagander | 2010-11-17 19:07:52 | Re: Re: [BUGS] BUG #5650: Postgres service showing as stopped when in fact it is running |