Re: SOC & user quotas

> I don't know, but in my opinion, I don't see anything bad in requiring
> dropping the data if the quota is full. That's what usually occurs in
> the case of normal filesystem quota... If you don't have a space there,
> you cannot edit files, copy them etc...
> And that solution should be definitely better than the filesystem quota
> for the PostgreSQL user for example.

The bad point is not that we would rollback the transaction. The bad
point is what happens when you need to rollback a transaction and in
your scenario it is quite plausible that a large rollback could occur,
more than once, causing the requirement of something like a vacuum full
to clean things up.

Sincerely,

Joshua D. Drake



> 
> regards,
>     Sergey
> *******************************************************************
> Sergey E. Koposov
> Max Planck Institute for Astronomy/Cambridge Institute for
> Astronomy/Sternberg Astronomical Institute
> Tel: +49-6221-528-349
> Web: http://lnfm1.sai.msu.ru/~math
> E-mail: math@sai.msu.ru
> 


-- 
     === The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive  PostgreSQL solutions since 1997            http://www.commandprompt.com/

Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate
PostgreSQL Replication: http://www.commandprompt.com/products/