| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | 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-04 20:10:11 |
| Message-ID: | 20141104201011.GD1791@alvin.alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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. Right now
it might not matter tremendously much given that we only extending a
page at a time, but there's also been talk about extending in larger
chunks and that could become a problem.
If someone were to indulge in actual thinking and less handwaving, I'm
sure it would be welcome.
--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | memtec | 2014-11-04 20:54:27 | Re: Incomplete startup packet help needed |
| Previous Message | Andres Freund | 2014-11-04 20:03:28 | Re: [BUGS] [HACKERS] COPY TO returning empty result with parallel ALTER TABLE |