X-Original-To: pgsql-admin-postgresql.org@postgresql.org Received: from localhost (wm.hub.org [200.46.204.128]) by postgresql.org (Postfix) with ESMTP id 5916A9FB212 for ; Fri, 8 Sep 2006 02:17:03 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.128]) (amavisd-new, port 10024) with ESMTP id 16218-05 for ; Fri, 8 Sep 2006 05:16:55 +0000 (UTC) X-Greylist: delayed 00:24:28.297218 by SQLgrey- Received: from svr4.postgresql.org (svr4.postgresql.org [66.98.251.159]) by postgresql.org (Postfix) with ESMTP id 4F5719FB21A for ; Fri, 8 Sep 2006 02:16:42 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.3 Received: from gourmet.spamgourmet.com (gourmet.spamgourmet.com [216.75.35.164]) by svr4.postgresql.org (Postfix) with ESMTP id 5F2C15AF03B for ; Fri, 8 Sep 2006 04:52:11 +0000 (GMT) Received: from gourmet.spamgourmet.com (localhost.localdomain [127.0.0.1]) by gourmet.spamgourmet.com (8.13.7/8.13.7) with ESMTP id k884q8s6010701 for ; Thu, 7 Sep 2006 21:52:08 -0700 Received: (from jqh1@localhost) by gourmet.spamgourmet.com (8.13.7/8.13.7/Submit) id k884q8r1010699 for pgsql-admin@postgresql.org; Thu, 7 Sep 2006 21:52:08 -0700 Received: from wx-out-0506.google.com (wx-out-0506.google.com [66.249.82.224]) by gourmet.spamgourmet.com (8.13.7/8.13.7) with ESMTP id k884q8mZ010694 for <>; Thu, 7 Sep 2006 21:52:08 -0700 Received: by wx-out-0506.google.com with SMTP id t13so505989wxc for <>; Thu, 07 Sep 2006 21:52:08 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type; b=Bhj3DbJzDJFevSKTRTXmiFYH8jU3a+T6zKC0Z6BxNoISsXvMYs6JEto043HrgE9n2rcXYJat7iHR0Wtbsu6n3r0ZLisITiMXXyTAwNqdIOmrS02RggMrgkV1FRNyOkbJbu6bFuag4oP6FIj4HZqN7iyd9/k0bwfg/cWsr8PZkcQ= Received: by 10.70.56.2 with SMTP id e2mr2026198wxa; Thu, 07 Sep 2006 21:52:07 -0700 (PDT) Received: by 10.70.44.9 with HTTP; Thu, 7 Sep 2006 21:52:07 -0700 (PDT) Message-ID: <1dbc7c340609072152n7eb70141u2b263ca43152ff6d@mail.gmail.com> Date: Fri, 8 Sep 2006 06:52:07 +0200 From: pgsql.maricau@a-bc.net To: pgsql-admin@postgresql.org Subject: dynamic or static MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_166174_4543235.1157691127126" X-Spamgourmet: X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=1.758 tagged_above=0 required=5 tests=HTML_00_10, HTML_MESSAGE, NO_REAL_NAME, UNPARSEABLE_RELAY X-Spam-Level: * X-Archive-Number: 200609/71 X-Sequence-Number: 22985 ------=_Part_166174_4543235.1157691127126 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Say you want to restrict the amount of used space on disk for Transaction log and/or Tablespace. There's the option "autoextended" on MySQL and a lot of other commercial DBRMS MS-SQL, Oracle and so on. That's for automatic growing the objects on the File Systems. But we can also put a static value so we have to change it if there is need for. On PostgreSQL do we have to use the quota's of the Operating System or what do we have to do for restricting the used disk space. ------=_Part_166174_4543235.1157691127126 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Say you want to restrict the amount of used space on disk for Transaction log and/or Tablespace.



There's the option "autoextended" on MySQL and a lot of other commercial DBRMS MS-SQL, Oracle and so on.
That's for automatic growing the objects on the File Systems.  But we can also put a static value so we have to change it if there is need for.

On PostgreSQL do we have to use the quota's of the Operating System or what do we have to do for restricting the used disk space.
------=_Part_166174_4543235.1157691127126--