| From: | Mark Kirkwood <mark(dot)kirkwood(at)catalyst(dot)net(dot)nz> |
|---|---|
| To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
| Cc: | Josh Berkus <josh(at)agliodbs(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: four minor proposals for 9.5 |
| Date: | 2014-03-20 08:47:59 |
| Message-ID: | 532AAB3F.3010809@catalyst.net.nz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 20/03/14 20:08, Pavel Stehule wrote:
>
>
>
> 2014-03-20 7:25 GMT+01:00 Mark Kirkwood <mark(dot)kirkwood(at)catalyst(dot)net(dot)nz
> Also I think this would probably only make sense for TEMPORARY
> tables - otherwise you can get this sort of thing going on:
>
> - you create a table and you have set a relation size limit
> - you commit and keep working
> - I add a whole lot of rows to your new table (taking it over the limit)
> - you go to add some more rows to this table...
>
>
> you cannot to across session limit and is not important if you do
> inserts more times or once.
>
Sorry Pavel - what you have said above is difficult for me to understand
- if the limit is intended as a *session* limit then concurrent activity
from multiple sessions makes it behave - well - strangely to say the
least, as tables are essentially shared resources.
Regards
Mark
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2014-03-20 08:59:33 | Re: four minor proposals for 9.5 |
| Previous Message | Marko Tiikkaja | 2014-03-20 08:01:37 | Re: Review: plpgsql.extra_warnings, plpgsql.extra_errors |