From ghanshyam@newgen.co.in Thu Aug 10 15:53:24 2006 X-Original-To: pgsql-admin-postgresql.org@postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id CC1459FB25E for ; Thu, 10 Aug 2006 12:53:24 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 29015-08 for ; Thu, 10 Aug 2006 12:53:14 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from newgen.co.in (mx.newgen.co.in [202.131.146.227]) by postgresql.org (Postfix) with SMTP id 4F0809FB2F8 for ; Thu, 10 Aug 2006 12:53:12 -0300 (ADT) Received: (qmail 25016 invoked by uid 507); 10 Aug 2006 15:53:11 -0000 Received: from 202.140.41.205 by mx.newgen.co.in (envelope-from , uid 501) with qmail-scanner-1.25 (fireav: ???. spamassassin: 3.1.3. Clear:RC:0(202.140.41.205):SA:0(-100.0/5.0):. Processed in 1.447974 secs); 10 Aug 2006 15:53:11 -0000 Received: from unknown (HELO ngmail.newgen.co.in) (okhlaoffice@202.140.41.205) by mx.newgen.co.in with SMTP; 10 Aug 2006 15:53:09 -0000 Received: (qmail 14964 invoked by uid 504); 10 Aug 2006 15:52:06 -0000 Received: from ghanshyam@newgen.co.in by ngmail.newgen.co.in by uid 501 with qmail-scanner-1.21 (fireav: ???. Clear:RC:1(192.168.5.190):. Processed in 2.821755 secs); 10 Aug 2006 15:52:06 -0000 Received: from unknown (HELO ng3024) (192.168.5.190) by 192.168.5.243 with SMTP; 10 Aug 2006 15:52:03 -0000 Message-ID: <002b01c6bc94$ec1cf420$be05a8c0@ng3024> From: "Sharma;G.S." To: Subject: Tempdb Date: Thu, 10 Aug 2006 21:22:02 +0530 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0028_01C6BCC3.05C46740" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.54 tagged_above=0 required=5 tests=AWL, HTML_30_40, HTML_MESSAGE, HTML_TEXT_AFTER_BODY X-Spam-Level: X-Archive-Number: 200608/138 X-Sequence-Number: 22681 This is a multi-part message in MIME format. ------=_NextPart_000_0028_01C6BCC3.05C46740 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi, can anybody tell me the How temporary tablespace management is done by = postgres . where the temdb is located , how to find out the space taken by tempdb . Thanks ------=_NextPart_000_0028_01C6BCC3.05C46740 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hi,
can anybody tell me the How temporary = tablespace=20 management is done by postgres .
where the temdb is located , how = to find out=20 the space taken by tempdb .
Thanks
 
 
Disclaimer :- This e-mail message including any attachment may contain confidential, proprietary or legally privileged information. It should not be used by who is not the original intended recipient. If you have erroneously received this message, you are notified that you are strictly prohibited from using, copying, altering or disclosing the content of this message. Please delete it immediately and notify the sender. Newgen Software Technologies Ltd and / or its subsidiary Companies accept no responsibility for loss or damage arising from the use of the information transmitted by this email including damage from virus and further acknowledges that any views expressed in this message are those of the individual sender and no binding nature of the message shall be implied or assumed unless the sender does so expressly with due authority of Newgen Software Technologies Ltd and / or its subsidiary Companies, as applicable. ------=_NextPart_000_0028_01C6BCC3.05C46740-- From smarlowe@g2switchworks.com Thu Aug 10 16:17:20 2006 X-Original-To: pgsql-admin-postgresql.org@postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id 5BB619FB1E9 for ; Thu, 10 Aug 2006 13:17:20 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 31123-07 for ; Thu, 10 Aug 2006 13:17:15 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from exchange.g2switchworks.com (mail.g2switchworks.com [63.87.162.25]) by postgresql.org (Postfix) with ESMTP id E93389FA502 for ; Thu, 10 Aug 2006 13:17:14 -0300 (ADT) Received: from 10.10.1.37 ([10.10.1.37]) by exchange.g2switchworks.com ([10.10.1.2]) with Microsoft Exchange Server HTTP-DAV ; Thu, 10 Aug 2006 16:17:13 +0000 Received: from state.g2switchworks.com by mail.g2switchworks.com; 10 Aug 2006 11:17:13 -0500 Subject: Re: Tempdb From: Scott Marlowe To: "Sharma;G.S." Cc: pgsql-admin@postgresql.org In-Reply-To: <002b01c6bc94$ec1cf420$be05a8c0@ng3024> References: <002b01c6bc94$ec1cf420$be05a8c0@ng3024> Content-Type: text/plain Content-Transfer-Encoding: 7bit Message-Id: <1155226633.20252.164.camel@state.g2switchworks.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 (1.4.6-2) Date: Thu, 10 Aug 2006 11:17:13 -0500 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.093 tagged_above=0 required=5 tests=AWL, SPF_PASS, UNPARSEABLE_RELAY X-Spam-Level: X-Archive-Number: 200608/139 X-Sequence-Number: 22682 On Thu, 2006-08-10 at 10:52, Sharma;G.S. wrote: > Hi, > can anybody tell me the How temporary tablespace management is done by > postgres . > where the temdb is located , how to find out the space taken by tempdb Slowly step away from the Oracle and everything will be OK. :) Seriously though, PostgreSQL doesn't use a separate temporary database for temp stuff, it uses a set of temporary schemas for temporary things. If you have temporary stuff, you'll see the schemas. test=> create temporary table abc (a int); CREATE TABLE test=> \dn List of schemas Name | Owner --------------------+---------- daily20051021 | postgres information_schema | postgres pg_catalog | postgres pg_temp_3 | postgres pg_toast | postgres public | smarlowe (8 rows) You can change your search path to one: test=> set search_path='pg_temp_1'; SET test=> \d List of relations Schema | Name | Type | Owner -----------+------+-------+---------- pg_temp_3 | abc | table | smarlowe (1 row) Note that tablespace management (quotas, etc.) are MUCH more primitive in PostgreSQL than in Oracle. This partly reflects the eras in which the two dbs grew up and what they were doing. Oracle grew up when 500 Meg RAID arrays were quite large, and space was expensive, and controlling the use of it was important. PostgreSQL "grew up" much later, when 500 Meg hard drives were door stops and controlling the use of disk space was often more bother than just adding on more drives to an array. Not that there's no need for quotes in postgresql, there is. It's just not been a priority for anyone to jump into. Now that we have table spaces, you can use those to control space usage by putting different things on differently sized drive arrays. Still kinda primitive, but it works.