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 1vlCCZ-008lmU-1i for pgsql-general@arkaria.postgresql.org; Wed, 28 Jan 2026 20:31:48 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1vlCCY-003cax-20 for pgsql-general@arkaria.postgresql.org; Wed, 28 Jan 2026 20:31:46 +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.96) (envelope-from ) id 1vlCCY-003cap-0k for pgsql-general@lists.postgresql.org; Wed, 28 Jan 2026 20:31:46 +0000 Received: from mail1.dalibo.net ([51.159.93.128] helo=mail.dalibo.com) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1vlCCV-00000000wC1-2bmO for pgsql-general@lists.postgresql.org; Wed, 28 Jan 2026 20:31:46 +0000 Received: from [192.168.1.128] (53.109.220.81.rev.sfr.net [81.220.109.53]) by mail.dalibo.com (Postfix) with ESMTPSA id 1787727C89 for ; Wed, 28 Jan 2026 21:31:42 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dalibo.com; s=a; t=1769632302; bh=Wn9DimbARrZbMpKjRD/DwkcctRPc0BCgCzkwwehBwR0=; h=Date:Subject:To:References:From:In-Reply-To:From; b=VsCR3WcRY50sxD/p3owy2kwsara+oMsYYMmUP/h+S90gLdWxYW02IeZBuS4V/n64Q +I4cyI2eqtC6LjFAGiJ/bfTPS+LWDfndkBqSmOtcNm2co3WMBjI+raBL/pgu+i30yD FQRbQ0cJ5hdMP6u1ehwe7wZ/UltuRiaWGHwFs1HY= Message-ID: <62048030-5073-4bfc-9565-f8af8084bf6c@dalibo.com> Date: Wed, 28 Jan 2026 21:31:41 +0100 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: About backups To: pgsql-general@lists.postgresql.org References: <1730736265.4259921.1769443263077.ref@mail.yahoo.com> <1730736265.4259921.1769443263077@mail.yahoo.com> <2097370962.4296686.1769449473672@mail.yahoo.com> <5efd76b75e527a6558dd69ba4364699f256a813a.camel@tpg.com.au> <259609552.3013229.1769632103875@mail.yahoo.com> Content-Language: fr From: Guillaume Lelarge Organization: Dalibo In-Reply-To: <259609552.3013229.1769632103875@mail.yahoo.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 28/01/2026 21:28, felix.quintgz@yahoo.com wrote: > The application is used in environments where there are no dba; in fact, the requirements specify that a dba cannot have access to the database, so signed records are used, trigger to prevent data changes, protection of protection triggers, etc. > Too many cases of theft. > > My role is DBA and developer at my organization, but the application is distributed to other companies. > The old application has been running unattended for over 15 years without problems in many companies without a DBA. > The certification body simply said it was written in a very outdated language and revoked its certification. Now I'm reprogramming it in a modern language and with a different database. > Almost all of my work has been with SQL Server and desktop applications. > > Cold and hot backups have taken me by surprise. > In SQL Server, I could perform a backup in the middle of user activity without any problems, so from what I had read about pg_dump, it was the same, but now I have many doubts. > > What happens if I start a backup in the middle of a user transaction? > The transaction can end before or after the backup ends, and it can also start before or after the backup begins. > Doesn't matter at all. You'll get a consistent backup. -- Guillaume Lelarge Consultant https://dalibo.com