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 1rPoIP-00EK51-Jp for pgsql-general@arkaria.postgresql.org; Tue, 16 Jan 2024 18:36:22 +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 1rPoIO-006NIV-ES for pgsql-general@arkaria.postgresql.org; Tue, 16 Jan 2024 18:36:20 +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 1rPoIO-006NIM-3m for pgsql-general@lists.postgresql.org; Tue, 16 Jan 2024 18:36:20 +0000 Received: from mail-oa1-x34.google.com ([2001:4860:4864:20::34]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1rPoIL-002A0m-T3 for pgsql-general@postgresql.org; Tue, 16 Jan 2024 18:36:19 +0000 Received: by mail-oa1-x34.google.com with SMTP id 586e51a60fabf-2046c724383so3802388fac.1 for ; Tue, 16 Jan 2024 10:36:17 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1705430176; x=1706034976; darn=postgresql.org; h=content-transfer-encoding:in-reply-to:from:references:to :content-language:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date:message-id:reply-to; bh=GkIJYux4QXZSHY2ErqGeEuqvJsMZ8g1MTalXgAWFRm8=; b=UwlyPoGGtksG3LS5SPhXVcPhODoPSPfm+27i63p5GosrjwZt6eyG6ZhDOzAjf4cVQs vXecvuteo/guSlP85hwpiuSrbx4yO5o6pOWC4MTxjViTZgLcygOz8fse5kzI97zkfWyZ NbxBNHoOCnebcEB1vtobvApQqR6daLps1vKblqc8tkcGPtB70ZJZp7tHxbSbfa/UI+xQ 5CXTvAkRVbh5ztjO+z/wLSAQEDzZWD2Jcmy5tTVkOZm2danR9O09BxQmLPyhb3mQMXWk ZUFU9msVhO5g4DDpiQJBn8A6V/d1S3Vg2BulgcSE7iq7ckunTF8iynq2pjG8vDevZt0P /foQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1705430176; x=1706034976; h=content-transfer-encoding:in-reply-to:from:references:to :content-language:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=GkIJYux4QXZSHY2ErqGeEuqvJsMZ8g1MTalXgAWFRm8=; b=QEjsJ5/d3B7fwFHPje24ANiqMtJu6LD52jBwkwCzyPwx6qyEojjTfHK+17sZbaXsOr 3eF68sGehrWx0Lvi/R2Hi9n9ON6P8N98XDIiiAIzqPHETpyzRE9huUQJaB21BMGr3kMN XFP6NMnpHTb4tIBG/fcbKUSGeK0SCio+3LtscO0yrnrgSiemGd49a7HRO4Cowj3khvHx McBi0eTSQ31Fe9I8anWuFCnXnUmUXqP0vk+zFV5K/ibytxAdW6a3dhRYs7tdG2SKWSs7 7UlcaDN3CVlCk2+XVbEKq67tLh7cFSgE8efsgrxi5XnmUAP+MJhndQHlWtRphQcJ++5L SpWg== X-Gm-Message-State: AOJu0YzmNDQ6YCznYrhyXa/oRU0UerrgNeAgk5k1E7PO/9JadykuxjTq DhvnsnHxao8XHauMCrYNEkKNHvY9WQ== X-Google-Smtp-Source: AGHT+IGi2MOMTnTL8keGivDIHaDoNeRNDEKv4IxOktzwy2Rn+Xj78njZ+s3Y2wGLVBb9vIi7+wdOxA== X-Received: by 2002:a05:6870:c38c:b0:204:71d:711d with SMTP id g12-20020a056870c38c00b00204071d711dmr5408293oao.65.1705430175887; Tue, 16 Jan 2024 10:36:15 -0800 (PST) Received: from [192.168.2.16] (070-113-014-216.res.spectrum.com. [70.113.14.216]) by smtp.gmail.com with ESMTPSA id t20-20020a05687044d400b002060e99b486sm3146092oai.22.2024.01.16.10.36.15 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 16 Jan 2024 10:36:15 -0800 (PST) Message-ID: Date: Tue, 16 Jan 2024 12:36:13 -0600 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: Moving to Postgresql database Content-Language: en-US To: Ron Johnson , pgsql-general References: <40a34680-1583-4cff-86cb-2598be16bb80@aklaver.com> <8cbd791a-0688-49fb-a536-3b8c30b5109b@aklaver.com> From: Jim Nasby In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 1/16/24 11:59 AM, Ron Johnson wrote: > >      > Hi. One of the biggest pitfall of PostgreSQL, from the app-dev > >     perspective, > >      > is the fact any failed statement fails the whole > transaction, with > >      > ROLLBACK as the only recourse. > > > >     "SAVEPOINT establishes a new savepoint within the current > transaction. > > > > > > I wish it was that easy. > > I've been scared away from using them, after reading a few > articles... > > Also, that incurs extra round trips to the server, from the extra > commands. > > The point was that '...  with ROLLBACK as the only recourse.' is not > the > case. There is an alternative, whether you want to use it being a > separate question. > > > Performance-killing alternatives are not really altternatives. What's the actual performance issue here? I'm also wondering what the use case for constantly retrying errors is. -- Jim Nasby, Data Architect, Austin TX