| From: | Marko Tiikkaja <marko(at)joh(dot)to> |
|---|---|
| To: | Atri Sharma <atri(dot)jiit(at)gmail(dot)com> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: replication_reserved_connections |
| Date: | 2013-07-28 10:23:23 |
| Message-ID: | 51F4F11B.7080501@joh.to |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 28/07/2013 08:51, Atri Sharma wrote:
> I would generally in agree with sharing super user reserved connections with replication.One thing I would like to explore is if we could potentially add some sort of priority system for avoiding contention between super user threads and replication threads competing for the same connection.
>
> We could potentially add a GUC for specifying which has the higher priority.
This sounds an awful lot like it would have to scan through the list of
existing connections, which I wanted to avoid.
Or maybe we could maintain a separate list of "reserved" connections,
i.e. ones that were created when we were at max_connections -
ReservedBackends? We could quickly look through that list to see how
many of which we have allowed. Not sure if that's practical, though.
Regards,
Marko Tiikkaja
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Stark | 2013-07-28 12:39:09 | Comparing toasted data (was improve Chinese locale performance) |
| Previous Message | Martijn van Oosterhout | 2013-07-28 09:39:40 | Re: improve Chinese locale performance |