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 1u67j5-00BXJc-Nq for pgsql-general@arkaria.postgresql.org; Sat, 19 Apr 2025 12:55:20 +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 1u67j3-00Dibn-05 for pgsql-general@arkaria.postgresql.org; Sat, 19 Apr 2025 12:55:17 +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.94.2) (envelope-from ) id 1u67j2-00Dibe-Ft for pgsql-general@lists.postgresql.org; Sat, 19 Apr 2025 12:55:17 +0000 Received: from mail-wm1-x330.google.com ([2a00:1450:4864:20::330]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1u67j0-000ruG-2y for pgsql-general@postgresql.org; Sat, 19 Apr 2025 12:55:16 +0000 Received: by mail-wm1-x330.google.com with SMTP id 5b1f17b1804b1-43cf06eabdaso25489335e9.2 for ; Sat, 19 Apr 2025 05:55:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cybertec.at; s=google; t=1745067313; x=1745672113; darn=postgresql.org; h=mime-version:user-agent:content-transfer-encoding:references :in-reply-to:date:to:from:subject:message-id:from:to:cc:subject:date :message-id:reply-to; bh=JIpU2XGz7yNs0lYUrCiMBrUcRbugQt9fAm4PGG2YRus=; b=o/FsA98KTurGIspOizbq8s8E/uGftcsiJbjnNmVtfcS5SX5bK6jeOxMlsq2dmLNQqg 7pWCo4rFbDRNKfKIvLlcpmOEa+DvYonsYstGv9vZnVIF/ocD96GDjp+K0lO8vWhwKprY 3p1U66w8W972WHw8FzYEqDg3SkxfLjHwvOlMSK0I5u2m1LX2xuwwHvNP3Fqeen6Gm0kt VCrN0TKV972bzStGzMNPZ++CasM0K3xrMwAG2hP4C/UraqEA3BxYtQ4Q0b7cPAAeduyG oHweoaTV61IbftlvwU/7AgoI28ynvBTpPVVcKm1v3mCCDNjJL08Fcl8iWaMTI8XGOYRK Bh+A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1745067313; x=1745672113; h=mime-version:user-agent:content-transfer-encoding:references :in-reply-to:date:to:from:subject:message-id:x-gm-message-state:from :to:cc:subject:date:message-id:reply-to; bh=JIpU2XGz7yNs0lYUrCiMBrUcRbugQt9fAm4PGG2YRus=; b=HOFf6CbUtTKm+bIqdrD2Mxa8pKJfsFx+ZKTtVgyhDk5J5pF2xGJb5HA2P5ZGqG14PS wD1taJuCZGu0lCX9368K5/RfDgl03eY71nfq2IefsQa4782TC9b1F75hmfEAJSft472N f9N2kTzRqEGZLZXneAQQ/WasugFIxKGePJKcWrMQW9cHBQge4+36XWawXwmXobBKxURY SE7flWGoOM3wfu43s97HR9ZjYdApFE6gkL6RV4m4oLPbpjrD5bIx3lrOequnksyObfpB Kv7k+lNnO7wH+0pDAf5I0JSNFwcqWCNn4e8VtmuIOeXNlErVqcMrHgUgpuN3uzw90C7E pteA== X-Forwarded-Encrypted: i=1; AJvYcCX1u7TLW7juw+DWn5s6oCtP4H5apIpNbz60DAT1+wTtCm7yjG23daPDXZS8MCaW5JSxlUAxAaSiGzHyPBhS@postgresql.org X-Gm-Message-State: AOJu0YyqkfLUhVPQYzZKVZIi6uE5oAthWEXZi7g0N8LsE7W6m1cAmEvr cW6yJGfDqMmezWwt5nu+BYwROMl+1xl0NnhnupodTrfyBx+T3BMi0AIsiAGNzxE= X-Gm-Gg: ASbGnctgw3mkUOznknVCjRgPjZ9TUd3QFdPBbX9tTwPkpjjQ09lSo+/YVTWGEca2Mms xqwdr3xaUTK8povkZWCm1iLRobNNovKdOP456NZgin4zHKVfJwU54nqPzzPS4/wpqVj5k2241cJ t8Cxx1iGZMsrxN5J2Xc1ulYdt3Ufpes0FSuFZvCkXiQw/tyJv3zIC2qoNBdF2GIcgbv+NkCjatu 7F/QW9TkvevV2IcLTspTm5Q22BhGNt5cIfkIM9B7Z6hH2cVhr3+I1Kr1ail7hyoFmUAefAwEvDK ok40k69sbRDz5hSDKfSaYdkfVesU3aus24TSJ3Cwsim8duXOHx5iAsphP9KxZg== X-Google-Smtp-Source: AGHT+IGQW4e8fPPwN7brQtn2d+LBQ5QnE+t1Xewy1kCxIXJRJQFTn/GjkRRfV43dr6UUszdBX3LrQg== X-Received: by 2002:a05:600c:a088:b0:43c:ec28:d31b with SMTP id 5b1f17b1804b1-4406ab9767bmr68309755e9.10.1745067313438; Sat, 19 Apr 2025 05:55:13 -0700 (PDT) Received: from localhost.localdomain ([2001:871:255:52d3:3ac8:61ab:b634:342]) by smtp.gmail.com with ESMTPSA id 5b1f17b1804b1-4406d5acc77sm60686575e9.10.2025.04.19.05.55.12 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sat, 19 Apr 2025 05:55:13 -0700 (PDT) Message-ID: <05820f63079333ff7e475e61b44c8378a03aa8e2.camel@cybertec.at> Subject: Re: Error while updating a table From: Laurenz Albe To: "sivapostgres@yahoo.com" , Pgsql-general Date: Sat, 19 Apr 2025 14:55:12 +0200 In-Reply-To: <45879321.3496225.1745066329503@mail.yahoo.com> References: <1385521371.3160626.1744955370756.ref@mail.yahoo.com> <1385521371.3160626.1744955370756@mail.yahoo.com> <02e2740edf821e2ce84773c83065b45e9be890cc.camel@cybertec.at> <1852089030.3173833.1744961512201@mail.yahoo.com> <24bb716bbdb6dbb8ac02c501db26731a101d21d3.camel@cybertec.at> <1365122733.3205645.1744975213857@mail.yahoo.com> <45879321.3496225.1745066329503@mail.yahoo.com> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable User-Agent: Evolution 3.54.3 (3.54.3-1.fc41) MIME-Version: 1.0 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Sat, 2025-04-19 at 12:38 +0000, sivapostgres@yahoo.com wrote: > So far, I couldn't find the query that caused the error.=C2=A0 =C2=A0Is t= here any way to unlock it?=C2=A0=C2=A0 >=20 > Re-start, Format and fresh install of windows, etc. ? On Windows you have to reboot, bow three times toward sunset, say a prayer to Bill Gates, then reboot again. No, seriously: randomly messing around with your machine rarely ever gets you closer to a solution. If you get the error current transaction is aborted, commands ignored until end of transaction= block it is 100% clear that an earlier statement in the same transaction must have got an error. Write your application so that it logs *every* error that comes from the database, then you are sure to catch that error. Also, if "log_min_messages" is "warning" (the default) or "error", you will find the error in the PostgreSQL log. That's all I can say to you. Yours, Laurenz Albe