<ruby id="bdb3f"></ruby>

    <p id="bdb3f"><cite id="bdb3f"></cite></p>

      <p id="bdb3f"><cite id="bdb3f"><th id="bdb3f"></th></cite></p><p id="bdb3f"></p>
        <p id="bdb3f"><cite id="bdb3f"></cite></p>

          <pre id="bdb3f"></pre>
          <pre id="bdb3f"><del id="bdb3f"><thead id="bdb3f"></thead></del></pre>

          <ruby id="bdb3f"><mark id="bdb3f"></mark></ruby><ruby id="bdb3f"></ruby>
          <pre id="bdb3f"><pre id="bdb3f"><mark id="bdb3f"></mark></pre></pre><output id="bdb3f"></output><p id="bdb3f"></p><p id="bdb3f"></p>

          <pre id="bdb3f"><del id="bdb3f"><progress id="bdb3f"></progress></del></pre>

                <ruby id="bdb3f"></ruby>

                合規國際互聯網加速 OSASE為企業客戶提供高速穩定SD-WAN國際加速解決方案。 廣告
                pg_upgrade upgrades a PostgreSQL cluster to a different major version. Usage: ? pg_upgrade [OPTION]... Options: ? -b, --old-bindir=OLDBINDIR??? old cluster executable directory ? -B, --new-bindir=NEWBINDIR??? new cluster executable directory ? -c, --check?????????????????? check clusters only, don't change any data ? -d, --old-datadir=OLDDATADIR? old cluster data directory ? -D, --new-datadir=NEWDATADIR? new cluster data directory ? -k, --link??????????????????? link instead of copying files to new cluster ? -o, --old-options=OPTIONS???? old cluster options to pass to the server ? -O, --new-options=OPTIONS???? new cluster options to pass to the server ? -p, --old-port=OLDPORT??????? old cluster port number (default 50432) ? -P, --new-port=NEWPORT??????? new cluster port number (default 50432) ? -r, --retain????????????????? retain SQL and log files after success ? -u, --user=NAME?????????????? cluster superuser (default "gjianbo") ? -v, --verbose???????????????? enable verbose internal logging ? -V, --version???????????????? display version information, then exit ? -?, -h, --help??????????????? show this help, then exit Before running pg_upgrade you must: ? create a new database cluster (using the new version of initdb) ? shutdown the postmaster servicing the old cluster ? shutdown the postmaster servicing the new cluster When you run pg_upgrade, you must provide the following information: ? the data directory for the old cluster? (-d OLDDATADIR) ? the data directory for the new cluster? (-D NEWDATADIR) ? the "bin" directory for the old version (-b OLDBINDIR) ? the "bin" directory for the new version (-B NEWBINDIR) For example: ? pg_upgrade -d oldCluster/data -D newCluster/data -b oldCluster/bin -B newCluster/bin or ? C:\> set PGDATAOLD=oldCluster/data ? C:\> set PGDATANEW=newCluster/data ? C:\> set PGBINOLD=oldCluster/bin ? C:\> set PGBINNEW=newCluster/bin ? C:\> pg_upgrade Report bugs to <[pgsql-bugs@postgresql.org](#)>.
                  <ruby id="bdb3f"></ruby>

                  <p id="bdb3f"><cite id="bdb3f"></cite></p>

                    <p id="bdb3f"><cite id="bdb3f"><th id="bdb3f"></th></cite></p><p id="bdb3f"></p>
                      <p id="bdb3f"><cite id="bdb3f"></cite></p>

                        <pre id="bdb3f"></pre>
                        <pre id="bdb3f"><del id="bdb3f"><thead id="bdb3f"></thead></del></pre>

                        <ruby id="bdb3f"><mark id="bdb3f"></mark></ruby><ruby id="bdb3f"></ruby>
                        <pre id="bdb3f"><pre id="bdb3f"><mark id="bdb3f"></mark></pre></pre><output id="bdb3f"></output><p id="bdb3f"></p><p id="bdb3f"></p>

                        <pre id="bdb3f"><del id="bdb3f"><progress id="bdb3f"></progress></del></pre>

                              <ruby id="bdb3f"></ruby>

                              哎呀哎呀视频在线观看