| From: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Alejandro Carrillo <fasterzip(at)yahoo(dot)es> |
| Cc: | Stephen Frost <sfrost(at)snowman(dot)net>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Tablespace limit feature |
| Date: | 2014-11-06 22:23:58 |
| Message-ID: | 545BF4FE.2090408@BlueTreble.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 11/4/14, 2:10 PM, Alvaro Herrera wrote:
> Alejandro Carrillo escribió:
>> >
>> >But This feature is very necessary to control the amount space expensed by a postgresql user or tablespace. This feature could be used in PostgreSQL Sharing Hosting, see: Shared Database Hosting - PostgreSQL wiki
> Sure. Rub hits the road when it comes to actually implementing this,
> though -- the issue of enforcing the limit without creating a bottleneck
> to table extension is not trivial to overcome, as I recall.
And index extension. And visibility map extension. And, and, and.
It's definitely a non-trivial problem to solve, and unfortunately there are extremely few hosting environment providers active in the community to even ask for the kinds of features they need, which means this just doesn't get much attention.
--
Jim Nasby, Data Architect, Blue Treble Consulting
Data in Trouble? Get it in Treble! http://BlueTreble.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephen Frost | 2014-11-06 22:43:01 | Re: Tablespace limit feature |
| Previous Message | Adrian Klaver | 2014-11-06 18:15:02 | Re: Postgres char type inconsistency |