Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1iPuw1-0008QT-Em for pgsql-bugs@arkaria.postgresql.org; Wed, 30 Oct 2019 20:51:17 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1iPuvy-0007Jf-OA for pgsql-bugs@arkaria.postgresql.org; Wed, 30 Oct 2019 20:51:14 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1iPuvy-0007JX-GI for pgsql-bugs@lists.postgresql.org; Wed, 30 Oct 2019 20:51:14 +0000 Received: from mail-qt1-x842.google.com ([2607:f8b0:4864:20::842]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1iPuvq-0000dv-QJ for pgsql-bugs@lists.postgresql.org; Wed, 30 Oct 2019 20:51:13 +0000 Received: by mail-qt1-x842.google.com with SMTP id y39so5290553qty.0 for ; Wed, 30 Oct 2019 13:51:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=2ndquadrant-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:subject:message-id:mime-version:content-disposition :content-transfer-encoding:in-reply-to:user-agent; bh=NVFBZCLzCAAiCxD70RF3F3oyQhraSvG5M8ik0dGcygk=; b=lxWmOaiJVnARC2kh4I5/pqRBoiY9eN36f0fPf1vbB24dOLYpXwccD5sxzsCVx8Dm8z 6b6YKAePVDJdKDFKYStKB2eNu/1PBSE9srNxm1vCCercX0i2FjMFQoz6nm4s72qu8zrH HCPnoMfQjMT7fgjI8mL3cvcwI/DO8ASDgq07eDJ38iQ5x6BJ7w+tNY7bufWHYDS+v8UM V11OldLX7sTpvFQEBY4v6aEr0i1zG2Oyy6MbbtoyItlDaEO0KwaSCbcQ7QaO0tUztUlp u4bIdXAf2yIDFxp9P7JANVPHYIMFkoVrKZX0mPmKTFOpjFD3tP82cC0W/FdUAotiicRN wJow== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:subject:message-id:mime-version :content-disposition:content-transfer-encoding:in-reply-to :user-agent; bh=NVFBZCLzCAAiCxD70RF3F3oyQhraSvG5M8ik0dGcygk=; b=dQT00YYZ8DMD2beXCVxg7I0tJN1k3SlPneI1LD1vnbQnfNFuULXjSOq9mp0R96Y39z M6fFqzdeLwayIetUdar/p+EZ99XPk9rkFB6Hj0DfyYU/hppQkHFV2zMjFnpew3HCSArx gtRavj2TkVSOUZTbzc3mLgBtfY6nnyjWSmxl9wgPO6nwpZ8gwl4eWjSURj8LozHNUjYI bCMcvvlq8ixOt4VrYjC+BUHUKSRKqO30fXwT0YRVleeVi574ygdmVZakxZR4DSxJB6TV JGiHvfHm/wA/iqS+lJ1wRnjw+D9M9KT7IW1LUP/qtf+z+V7papwBvs60R55jcnEt531U F/Vg== X-Gm-Message-State: APjAAAWwiX1zf44zsVLKMHLQDF04uUQ+rx82uXCZ2WltAQxiPoCCw2Jd DEJA28QTwOR19TnShJkHzniwqLRDtf7JDXVDh7E2M9zr9D9OLxgzGSa4vGV/A7YSHQRtimpxQOF lP4l0WJGfJ5xpRpu0t+29e3hjeSx0wpPcsLHyGun1qoZz/ebg9bp5QvS84VrRC7Z7DshRd1KrX7 o+81AOAHT90Q== X-Google-Smtp-Source: APXvYqx5R/Gf02bXc2KqeZ/Bqm5S9Wif0ZEFuJJ13MrHpcqcRBIRIb9bw4JxEnv6Sism6PrvqJndHg== X-Received: by 2002:ac8:117:: with SMTP id e23mr2119068qtg.82.1572468664943; Wed, 30 Oct 2019 13:51:04 -0700 (PDT) Received: from nimloth.alvh.no-ip.org ([179.56.30.174]) by smtp.gmail.com with ESMTPSA id r126sm657823qke.98.2019.10.30.13.51.04 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 30 Oct 2019 13:51:04 -0700 (PDT) Received: by nimloth.alvh.no-ip.org (Postfix, from userid 1000) id 231FF300A9F; Wed, 30 Oct 2019 17:51:02 -0300 (-03) Date: Wed, 30 Oct 2019 17:51:02 -0300 From: Alvaro Herrera To: rgonzalez@spensiones.cl, pgsql-bugs@lists.postgresql.org Subject: Re: BUG #16090: =?iso-8859-1?Q?Migraci=F3?= =?iso-8859-1?Q?n?= con pg_dump Message-ID: <20191030205102.GA6361@alvherre.pgsql> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <16090-d6ea11d1c8db11a7@postgresql.org> User-Agent: Mutt/1.10.1 (2018-07-13) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Hello pgsql-bugs, this is bug #15955 :-) PG Bug reporting form escribió: > Alvaro Herrera: > > El problema que te comenté en pgDay es el siguiente: > Al tratar de realizar la migración de postgres versión 8.4 a 11.5 utilizando > pg_dump, es decir: > pg_dump -h IP_Servidor8.4 -U postgres -d BD -n Squema | psql BD -U postgres > entrega el siguiente error: > > pg_dump: [archiver (db)] query failed: ERROR: relation "pg_opfamily" does > not exist Hola Regina, como te comenté por correo privado, ese bug fue resuelto recientemente y la corrección estará publicada junto con 11.6 en un par de semanas más. -- Álvaro Herrera https://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services