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.96) (envelope-from ) id 1vkQwn-00F6Xg-0k for pgsql-general@arkaria.postgresql.org; Mon, 26 Jan 2026 18:04:21 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1vkQwm-009uKa-0d for pgsql-general@arkaria.postgresql.org; Mon, 26 Jan 2026 18:04:20 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vkQwl-009uKS-2M for pgsql-general@lists.postgresql.org; Mon, 26 Jan 2026 18:04:20 +0000 Received: from smtp119.iad3a.emailsrvr.com ([173.203.187.119]) by makus.postgresql.org with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vkQwi-002QuI-2a for pgsql-general@lists.postgresql.org; Mon, 26 Jan 2026 18:04:18 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=g001.emailsrvr.com; s=feedback; t=1769450656; bh=rI9Rzw/PwbVJgcQ1n0vM2iK036+b9H56mKhhedgE6Is=; h=Subject:From:Date:To:From; b=FvVptFB8XXHiNt/v/7AtH/I6LmaNJPmdNXq3tuS/e+3SOGHiekhbssYnyL9lD1zsw 4dOzXci4fkmKI53E3hL4YUu9DcwwKHTDayN1JLJAQHt+1x7msq2Vo+HXQrK3yv1m9L SrPjaQ5wIMeiSpT5ICFHqhJ5XYaPPNAKMePazn6c= X-Auth-ID: xof@thebuild.com Received: by smtp31.relay.iad3a.emailsrvr.com (Authenticated sender: xof-AT-thebuild.com) with ESMTPSA id 3F26C249A3; Mon, 26 Jan 2026 13:04:16 -0500 (EST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3776.700.51.11.8\)) Subject: Re: About backups From: Christophe Pettus In-Reply-To: <868938296.4311067.1769449951678@mail.yahoo.com> Date: Mon, 26 Jan 2026 10:04:15 -0800 Cc: pgsql-general@lists.postgresql.org Content-Transfer-Encoding: quoted-printable Message-Id: <06150340-D824-4F4D-A68A-EA205908431F@thebuild.com> References: <1730736265.4259921.1769443263077.ref@mail.yahoo.com> <1730736265.4259921.1769443263077@mail.yahoo.com> <868938296.4311067.1769449951678@mail.yahoo.com> To: felix.quintgz@yahoo.com X-Mailer: Apple Mail (2.3776.700.51.11.8) X-Classification-ID: 7b952e83-2ba7-45a6-983e-8154ea396ee7-1-1 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk > On Jan 26, 2026, at 09:52, felix.quintgz@yahoo.com wrote: >=20 > I'm having a problem with this. I'm repurposing an old application = written in Visual Basic 6 that did allow backups through signed stored = procedures.=20 > This is a requirement for financial applications; the user can perform = a backup whenever they want, but they can't access the database. > The new application is web-based, deployed in containers, and the = database server container is not the same as the application's, so I = can't use pg_dump in the application, or at least I don't know how to do = it. There is currently no supported way of backing up a PostgreSQL database = via an SQL command. You could, in theory, use the COPY command to dump = each individual table, but that's probably not what you are looking for = (since it would also require a fairly sophisticated restore process). pg_dump can run in the application container, and connect to the = database in the database container, just like the application does. = There's no requirement that pg_dump run on the database host. That's = probably the best direction in this case.=