Re: four minor proposals for 9.5

From: Mark Kirkwood <mark(dot)kirkwood(at)catalyst(dot)net(dot)nz>
To: Josh Berkus <josh(at)agliodbs(dot)com>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: four minor proposals for 9.5
Date: 2014-03-20 06:25:00
Message-ID: 532A89BC.2010300@catalyst.net.nz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 20/03/14 13:28, Josh Berkus wrote:

>> 3. relation limit - possibility to set session limit for maximum size of
>> relations. Any relation cannot be extended over this limit in session, when
>> this value is higher than zero. Motivation - we use lot of queries like
>> CREATE TABLE AS SELECT .. , and some very big results decreased a disk free
>> space too much. It was high risk in our multi user environment. Motivation
>> is similar like temp_files_limit.
>
> I'd think the size of the relation you were creating would be difficult
> to measure. Also, would this apply to REINDEX/VACUUM FULL/ALTER? Or
> just CREATE TABLE AS/SELECT INTO?
>

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...

Should you now be stopped working? Does this feature need to track *who*
added which chunks of a table (suspect very difficult to do sensibly)?

Regards

Mark

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Kyotaro HORIGUCHI 2014-03-20 06:43:00 Re: Archive recovery won't be completed on some situation.
Previous Message Kyotaro HORIGUCHI 2014-03-20 06:17:55 Re: Archive recovery won't be completed on some situation.