Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1r5nEk-00F5MM-NW for pgsql-general@arkaria.postgresql.org; Wed, 22 Nov 2023 13:25:50 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1r5nEi-008buy-Oi for pgsql-general@arkaria.postgresql.org; Wed, 22 Nov 2023 13:25:48 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1r5nEi-008buq-Dr for pgsql-general@lists.postgresql.org; Wed, 22 Nov 2023 13:25:48 +0000 Received: from sonic319-22.consmr.mail.ne1.yahoo.com ([66.163.188.84]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1r5nEg-007mjQ-0P for pgsql-general@lists.postgresql.org; Wed, 22 Nov 2023 13:25:47 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1700659543; bh=d6zA9i8F0VBSA3A+7kDuU7s9Vg3ptwpHeWeJ0Gm8vbs=; h=Date:From:To:Subject:References:From:Subject:Reply-To; b=ugytnteR3MBwDn0z6+RbS1aMSDWW9V2KnDhgy95pSNbrXKddDXvSWTvsWviDk1mJGVW7Z7MZDHZyZEujga3GWlq+MdUWc7xuv2vi9BtGvBgm7kOtz4sUo4i6Djltup5QNnvna7dDe7+IpZJyIGF+4tJBAs/5BZMA9DRm6+dXNWWmPFXQI6Z6VvgJdRPARy4eRI2wKDCv/CDj0qmXf1i+jE9QnOdU0SG4AcwBJL/4aKBEOmtE18V/UX9NQ3pRl/4Rn2B/HfLgjPmB2AbX/w6mAufjU2HPhPhVfR4H2lbcrBZ23xW4kUiqsW/gQAqJTj3j2TQ8yiGdqv3pYk05v72aHw== X-SONIC-DKIM-SIGN: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1700659543; bh=KCI6XgH3/3mWIS+ORj+c49xPbKigNIAgB+uFftzf6Bz=; h=X-Sonic-MF:Date:From:To:Subject:From:Subject; b=RxczALZjFyp1ZNvSHaTuJh2A7L/XbqBDxFHmHDFwMX5y7y+oOIXy9j1VNa+zJuTCFlk8ntG27dtMx4lHcbyMcLkMHlsfQTJt7D620+vghIEu3D4AUgRv229AoSWLsdj3bm/8AoTiQd+5IAj4/nRLUNfPRooeTwa9xpeQQExMUdHSy8J6Ap/JfhFOARyT6sXTgMXsiLf6i7RQLlA/S9vTpdjnL0gKDKUi73h1ozkfauAYToBC9N1u8ZhbIPP3PU0wfnCmthfsMxOXb7TmX63ODLb6phiLDhICzZ6IHoD//pXBZyWV8LKNzihGlQg6aKGVA+0HdQwrPHHO+5GMCx3mbw== X-YMail-OSG: I5P4hE0VM1m81cWonlo4T0.LruEA7TBWbfiO6NgpkVUTkfVpSNRZGUhujQHv6Wv w3j9TLgq40ya9ZBD1WHHbl_M1kQuRkDFhG9EpuNoJozAAENR3HTA6DScU4EVRAUyjQr3dFgb5u8R csn75j6CrsGuCquzLLZFg7R.KhieaW_0olqGDrCe_tvzaeDO0HCmRFXApNqRbzcBlsjG.x19a0V_ cNAJ9fMOCHu34c.W9u.GfSzVfg3CD2rThsyjmPFfxMfkTQXJEd3oteo2BqRnLkQdi8WU5eF0LGfL N1zxpWdzKdpqzDPm4jo0GNcnr9y6z91zpgJ_Oes8xsuhrvg3bArBOobjVlDh22xCYSApxlXIXaCV TSietGh0AhyDr10eEzgqzZ5gLIFxVpZ2P_J3QWzJybbgrwzCqT4q9P40OCtIk8KXxYVPuz2aRn6b 1vW0NTCyE7jRqhmSCWgekWxLm.aGqUCSNYZfFJJrwEZ9QdYgvEphvMODHKJBD29Ko5I30tFQHUtJ AiYH6iRh2vNBiswkBNbPihng7jWX1SV3QVrfm5jN9MFTqUp33hXplvVOv3u9rpEjohfxkBBIL_.a F2bEnvDokiKSJdup.eo1BPa0wyJGR55GovU6iU9fUWET0eNcRsH4qnIM8p0x3IS8t4DeeZfEwyiw vYhbLpj9c9IcZhqkxKhXrloOQ00tFyx948xstJ4JL1vqGV_K7UWNvgKU3yUthdcWfvEKxm7BNNAD vcamJB9WyXapaGkEu4GELU4kCF7vCjpgMturrbpS.1HqqyjfwGdSL_7giU7VE438HicybkU6hWoY bjfp27549v8h5Df5gLPUOHME3VkehHQdmJntVBm3vNMpsM2hdaaKg9XWPDSk9TR2HXGupP_99CVD yNao00ckoQe8r2Z3fyQ3K392extiuJjhr.oyHNJ1bQLTwHVCB2_3GyW79GUmNUejjQiHvu5c55lX H26.G.WOoL_vnsv4AnxaAGBtLo9WioJEuya9n1jVfDX_I8M3Xzfdj2RAIZdSYNuzBRB5XR52f_dl MwAcDkapTvQ6s8iO6zlCPFmkuJzVe0O6FGrMtlN.NEomko60m4lGH7ioaMCpn9RtkfCQv1nMTKuR dTboI.39noMXFLYBI3ShtUhpURFpEiRRtoFLWOjjps1hYKJ.aFmn1lkcGe6dBVIePfL_p93HAuVr 8.NJEtGqmM15nykG3oZdqwOsXNUWpUZcZuqI2NQlV1n6QVfrznBcEGVZdShQyy4eyRXc_m8o852j oKt.Otlz08DKjdR9gxcI7KHpKaS6D1IWV0V9uye8jONopw6v.cLpxSdJrkz2Fs6_zNLU4m6cdeRG 39CZANVwq5zP9yGQ3_fxiHgzldZjeuubSu2G5.RKNJH2xgykwGd0OXlDz_UUe4QiGrI76kADqtCW 0r5vM7Qsglh3IihDdGBA68em3ksWeorURQmnkjTWz7DGEtA5FbpjOMT_Ut5eY1IX47aB5wf.siwB dD5NFm2DoR6lfqqWKmJPt7A20mSiRgXUvSs6H0lVWW2uIGNmgf.8ySjZs42GPoyKkrk_droInhYB j39ujBTBwgZdmilBogSzO.4GRnI8sMe.r56N5WmznCVp1cO7Pkfse_se8mJSwTj7KY4JuefuKnK0 821iNDziTzrZHtScpteJiX73jW6.nFpyByQcPPRlOWqOtnq8_gaTVKfznFl.fVCwCbgY2L82Xf6a 99Qu6lZL8rZQBiEot52nMe9vWWPmD22oX8MKIU1cG61Mxv1SvJZOy5Btp8DzX3NVfJOtsVpbIwCa _qdt5T9AegtYmbIHDeAc4SBQML8HTrwdhm7w10qRjFfs9E1ycesAtW3bEYQgMeGCMvFszv5gxL82 8MebvlQWvOjzGDa9abnAdInfOEwm.3JWyHKlKDnt5DHlRwDYHOaiJzKI5x_8FpS2.w0X1Vzf91eH xVuFCtlKYsCHTR4WFhPg6Seo7WJZ.lRW3wsjzwFyEcMROAsFd9ki8VwfO1IZIn3sWZTl1EqqI7Rm uMMDq_Tpj1qwgWu9LDZWRXepH2M6tGH0_HGAGNut.onLXKBwvvJZpXD33hbMlhkCBatwYhw4M6jl mPQUdYP__scZrlsoqql5otj6Tp.CANxt04b0._ozx6x2Gn8rpjJwVPSbwFgsNBrH04o8KwB3fs4E 2ZIsf5odaBCviOsuvnlU_7htTAfPRzQC_HVsRGHpdmG_6x0v2jlzX1epOXjjnT2dlrGoxarY- X-Sonic-MF: X-Sonic-ID: 29491332-3bc5-4f18-b93d-fc0588a66449 Received: from sonic.gate.mail.ne1.yahoo.com by sonic319.consmr.mail.ne1.yahoo.com with HTTP; Wed, 22 Nov 2023 13:25:43 +0000 Date: Wed, 22 Nov 2023 13:25:40 +0000 (UTC) From: "Efrain J. Berdecia" To: "pgsql-general@lists.postgresql.org" Message-ID: <362032628.6955904.1700659540303@mail.yahoo.com> Subject: pg_restore enhancements MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_6955903_274097175.1700659540301" References: <362032628.6955904.1700659540303.ref@mail.yahoo.com> X-Mailer: WebService/1.1.21896 YMailNorrin Content-Length: 2924 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk ------=_Part_6955903_274097175.1700659540301 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit After working for a site where we are constantly doing logical pg_dump to refresh environments I've come to miss features available in other RDBMS' refresh/restore utilities. Someone could point me in the right direction otherwise, but pg_restore seems to be lacking the ability to resume a restore upon failure, is all or nothing with this guy. There also doesn't seem to be a way to control batch size when doing the COPY phase, therefore preventing the WAL directory from filling up and crashing the system. IMHO, it would be nice to have a feature that would allow pg_restore to resume based on which part of the restore and/or object have already been restored. When it comes to the COPY phase of the restore, it would be nice to be able to control batch size and resume COPY of a particular object upon failure. Thanks in advance for any suggestions or the green light to post this to the PG-developer group :-) Thanks,Efrain J. Berdecia ------=_Part_6955903_274097175.1700659540301 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
After working for a site whe= re we are constantly doing logical pg_dump to refresh environments I've com= e to miss features available in other RDBMS' refresh/restore utilities.

Someone could point me in the right direction otherwise, but= pg_restore seems to be lacking the ability to resume a restore upon failur= e, is all or nothing with this guy. There also doesn't seem to be a way to = control batch size when doing the COPY phase, therefore preventing the WAL = directory from filling up and crashing the system.

IMHO, = it would be nice to have a feature that would allow pg_restore to resume ba= sed on which part of the restore and/or object have already been restored.<= /div>

When it comes to the COPY phase of the restore, it would = be nice to be able to control batch size and resume COPY of a particular ob= ject upon failure.

Thanks in advance for any suggestions = or the green light to post this to the PG-developer group :-)
Thanks,
Efrain J. Berdecia
------=_Part_6955903_274097175.1700659540301--