| From: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
|---|---|
| To: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Hot Standby: subxid cache changes |
| Date: | 2009-02-13 11:07:32 |
| Message-ID: | 49955474.9000702@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Simon Riggs wrote:
> I think my proposal still holds water, but I also think it is probably
> time to say OK, let's make this simpler and take the subxid tuning off
> line.
Agreed.
> We would need to increase the max size of the xip array by
> 2*max_connections. So an increase of 80kB on normal running, which I can
> accept.
You only need the bigger xip array while in hot standby mode. Backends
starting after the recovery is done can use just max_connections. And
you were already allocating a bigger subxip array, so the net effect is nil.
> Is that the only change you are suggesting to resolve this? I hope so.
Yes.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Teodor Sigaev | 2009-02-13 12:06:15 | Re: GIN fast insert |
| Previous Message | Simon Riggs | 2009-02-13 10:59:37 | Re: Hot Standby: subxid cache changes |