Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1cTwfx-000584-Hq for pgsql-admin@arkaria.postgresql.org; Wed, 18 Jan 2017 20:17:45 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1cTwfw-0004Ya-Uo for pgsql-admin@arkaria.postgresql.org; Wed, 18 Jan 2017 20:17:44 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1cTwfw-0004Y5-3w for pgsql-admin@postgresql.org; Wed, 18 Jan 2017 20:17:44 +0000 Received: from tamriel.snowman.net ([72.66.115.51]) by makus.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1cTwfr-0007If-72 for pgsql-admin@postgresql.org; Wed, 18 Jan 2017 20:17:42 +0000 Received: by tamriel.snowman.net (Postfix, from userid 1000) id CA1355F794; Wed, 18 Jan 2017 15:16:38 -0500 (EST) Date: Wed, 18 Jan 2017 15:16:38 -0500 From: Stephen Frost To: "Ferrell, Denise D CTR NSWCDD, H11" Cc: "pgsql-admin@postgresql.org" Subject: Re: PostgreSQL 9.3 ERROR Message-ID: <20170118201638.GD18360@tamriel.snowman.net> References: <2BC18916DE4BF141AC1EFC55CE2CAE7D36C5A44F@NAEANRFKXM01V.nadsusea.nads.navy.mil> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="TRTrqq5C0A9KK7Rj" Content-Disposition: inline In-Reply-To: <2BC18916DE4BF141AC1EFC55CE2CAE7D36C5A44F@NAEANRFKXM01V.nadsusea.nads.navy.mil> X-Editor: Vim http://www.vim.org/ X-Info: http://www.snowman.net X-Operating-System: Linux/3.13.0-91-generic (x86_64) X-Uptime: 15:12:38 up 193 days, 21:36, 2 users, load average: 0.01, 0.07, 0.14 User-Agent: Mutt/1.5.21 (2010-09-15) X-Pg-Spam-Score: -5.1 (-----) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-admin Precedence: bulk Sender: pgsql-admin-owner@postgresql.org --TRTrqq5C0A9KK7Rj Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Greetings Denise, * Ferrell, Denise D CTR NSWCDD, H11 (denise.ferrell.ctr@navy.mil) wrote: > Running on Linux...has anyone else encountered this? >=20 > Receiving the following error in the pg_log file: >=20 > "could not extend the "pg_tblspc/23917/PG_9.3_201306121/16385/55041.5": w= rote only 4096 of 8192 bytes at block 722183" That error indicates that the filesystem ran out of disk space. > I was under the impression that PostgreSQL allocates 1G per tablespace fi= le. That is incorrect. In PostgreSQL, a "tablespace" is a directory. Every table in PostgreSQL consists of a set of files. None of the individual files for a PostgreSQL table will be larger than 1G, but PostgreSQL will use multiple files when it reaches 1G in size. In the above case, the table/index with relfilenode 55041 in the database with oid 16385 has grown to be over 5G in size. The files: 55041 55041.1 55041.2 55041.3 55041.4 55041.5 are all associated with that table/index. Thanks! Stephen --TRTrqq5C0A9KK7Rj Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBCgAGBQJYf80mAAoJEO1sijiDR2RVgAEQAK4t4XDkAKYtP+98JvQFhAXU Ak5MLCBP9JUa94tTs6AseZ8Jyh+XrBbzu0le8NXLhYN54TsqapRylN/33ns7HQcz hgOPjkhNfHl31l0KTBfQaGMUVORARM0pQ3MHoR7lpI/g23jRxpTwuNd2qB1y+b0o fHI7wTeORhAIUROa5dz4Qr8/55CmBtDmhxW8h28eubxe+4pfqcY3WCfRStTBKyAz YCi8HhYmhOtQ2eQ4hpikmLAGKUnZwgiefgEd6waXVEgU3vvCCOkxE77hvpUC6oV1 /koOBCfpyDHVXG98iRZj07DTChFg98F+TtAS2N5v8MRN0BAhNjaEQIds4jHrZtUR N6/DJWiCZoZuoHJgrYCSjYPrdmBwEYNgYcn8hN/Yle610KY2HeL2Qtt57KuBaawP m9vlO74AxFcsWYk0yfa+Gxd4DyFOTGSsHVUWorj0xOLJ9cNqBpl7j7SqjxLT8YwB UtEBvGkJNcBHrj46kAgkzui4VQ3cvwhfzCON5q+MsXq/6sN3KHEJeDQu5uxXeYdB tYut/1oOTCGmKnlarDh5a05VNJ/k4TQuKC+M4gsRP2fhwTebjAuWQQU2tdAKWECm gByIospTGKXL95qFG5OqH+c5BnkCHHSqC9knCizLwod+77+BxDfBLykYSIdJcmi9 at00+ZHS8cAmQTmsp8t7 =/lD3 -----END PGP SIGNATURE----- --TRTrqq5C0A9KK7Rj--