Message-ID: <4EA5E5D1.8020804@cisco.com>
Date: Mon, 24 Oct 2011 16:25:21 -0600
From: Krishnamurthy Radhakrishnan <kradhak@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6;
	rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1
MIME-Version: 1.0
To: Kevin Grittner <Kevin.Grittner@wicourts.gov>
CC: pgsql-admin@postgresql.org
Subject: Re: Dumping data using pg_dump after chrooting to a different
	partition
References: <4EA5E253.6020600@cisco.com>
	<4EA59DB50200002500042527@gw.wicourts.gov>
In-Reply-To: <4EA59DB50200002500042527@gw.wicourts.gov>
Content-Type: multipart/alternative;
	boundary="------------010200020206070505030401"

This is a multi-part message in MIME format.
--------------010200020206070505030401
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Hi Kevin,

Can you please elaborate how to do the following?

connecting through a TCP connection and piping directly
from pg_dump to psql

Since we could have DB schema changes between the versions, we may not 
be able to copy the data directory.

Does pg_upgrade support changes to the schema?

Thanks.

Radha

On 10/24/11 4:17 PM, Kevin Grittner wrote:
> Krishnamurthy Radhakrishnan<kradhak@cisco.com>  wrote:
>
>> pg_dump works before chrooting to the secondary partition. Can
>> you please provide a way to dump the data after chrooting?
>
> How about connecting through a TCP connection and piping directly
> from pg_dump to psql?
>
> Of course, these days you have the option of just using pg_upgrade
> against the original or a deep copy of the data directory.
>
> -Kevin


--------------010200020206070505030401
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    Hi Kevin,<br>
    <br>
    Can you please elaborate how to do the following?<br>
    <br>
    <font color="#009900">connecting through a TCP connection and piping
      directly<br>
      from pg_dump to psql<br>
    </font><br>
    Since we could have DB schema changes between the versions, we may
    not be able to copy the data directory.<br>
    <br>
    Does pg_upgrade support changes to the schema?<br>
    <br>
    Thanks.<br>
    <br>
    Radha<br>
    <br>
    On 10/24/11 4:17 PM, Kevin Grittner wrote:
    <blockquote cite="mid:4EA59DB50200002500042527@gw.wicourts.gov"
      type="cite">
      <pre wrap="">Krishnamurthy Radhakrishnan <a class="moz-txt-link-rfc2396E" href="mailto:kradhak@cisco.com">&lt;kradhak@cisco.com&gt;</a> wrote:
 
</pre>
      <blockquote type="cite">
        <pre wrap="">pg_dump works before chrooting to the secondary partition. Can
you please provide a way to dump the data after chrooting?
</pre>
      </blockquote>
      <pre wrap=""> 
How about connecting through a TCP connection and piping directly
from pg_dump to psql?
 
Of course, these days you have the option of just using pg_upgrade
against the original or a deep copy of the data directory.
 
-Kevin
</pre>
    </blockquote>
    <br>
  </body>
</html>

--------------010200020206070505030401--