X-Original-To: pgsql-docs-postgresql.org@localhost.postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id F268B9F96B6 for ; Wed, 10 May 2006 01:44:58 -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 35188-07 for ; Wed, 10 May 2006 01:44:54 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id 0CAF59F931D for ; Wed, 10 May 2006 01:44:53 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.6/8.13.6) with ESMTP id k4A4iooh026328; Wed, 10 May 2006 00:44:50 -0400 (EDT) To: Bruce Momjian cc: Mark Stosberg , pgsql-docs@postgresql.org Subject: Re: pg_dump docs should mention TMPDIR In-reply-to: <200605100313.k4A3DlW18221@candle.pha.pa.us> References: <200605100313.k4A3DlW18221@candle.pha.pa.us> Comments: In-reply-to Bruce Momjian message dated "Tue, 09 May 2006 23:13:47 -0400" Date: Wed, 10 May 2006 00:44:50 -0400 Message-ID: <26327.1147236290@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200605/26 X-Sequence-Number: 3553 Bruce Momjian writes: > Mark Stosberg wrote: >> Is that any concern that over time newer pg_restore's won't read old >> "custom" formats? That would be my only worry-- that the data would be >> locked in a binary format which becomes unsupported. > No, we wouldn't do that. Right, I can't imagine that we'd abandon support for pg_dump custom format without many versions' warning. AFAIK we still read pg_dump output from 7.0 if not earlier ... regards, tom lane