Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1oWzU9-000292-Jl for pgsql-bugs@arkaria.postgresql.org; Sat, 10 Sep 2022 12:21:21 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1oWzU6-0001Xv-HQ for pgsql-bugs@arkaria.postgresql.org; Sat, 10 Sep 2022 12:21:18 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1oWzU6-0001Xk-4s for pgsql-bugs@lists.postgresql.org; Sat, 10 Sep 2022 12:21:18 +0000 Received: from mail-qk1-x736.google.com ([2607:f8b0:4864:20::736]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1oWzTz-0003cq-96 for pgsql-bugs@lists.postgresql.org; Sat, 10 Sep 2022 12:21:15 +0000 Received: by mail-qk1-x736.google.com with SMTP id c9so3019089qkk.6 for ; Sat, 10 Sep 2022 05:21:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=systemguards-com-ec.20210112.gappssmtp.com; s=20210112; h=in-reply-to:content-transfer-encoding:content-disposition :mime-version:references:message-id:subject:cc:to:from:date:from:to :cc:subject:date; bh=dqUYAbM7JTxCkyR0UC4aI8a7eVvCIXAC9Q8U7cWmsAo=; b=p7pTM4gOKm4CuC1OnCB+Wh1EpF4IIQ0FjoqFX/CvX/nK2fHXAS1k0+NEvWJaf+HWpE ODvN2hD9JcMrqYu1DEkxE/oyCaDs5Xbq75/s5wDXQS8ZRBRwK5BpwyvFyhVTu9dGnkVt ekWxaaWH2wIOOdVsrI0/LHyfL7a+6SSBrDne84pIL84JH6oyMcyq4Z8rw+H0uX7rAyuS jF1z/LkEaqDdsLY7/dKAOJbgMKruo7mvL8Zz0sruIsWVuaLXBinsdAshp2HpcTVGvtpm 2PMmDf0HOTXmC8dnTvDQh+DyKJ4I8SRSVsf+NyqErAj5EoNh55RaBMeYS5p/S9GqFabn nkAw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=in-reply-to:content-transfer-encoding:content-disposition :mime-version:references:message-id:subject:cc:to:from:date :x-gm-message-state:from:to:cc:subject:date; bh=dqUYAbM7JTxCkyR0UC4aI8a7eVvCIXAC9Q8U7cWmsAo=; b=8D21mupZSLuawbGkaMFIZTgsif5jPoU8tD4hENEwU9gQq4zcJsn6w+O56qlqGyYunA Zi6SmdvmkBrZtqewX1FIGdLmLVA4BjzCQx5iQ+gBU4h/AU6ev27yc74qI65Uc3BHF7xy Esm74pq3TPqOXyWBaBACf0TV9Y02eQ5tPq2iCx5RiD1B3BEHlU5dqCGvQ7xRf697xvgd FwRvUcvEMQvHtvvzj1yGmUPaj8KsBNOdrlI9fIdNcH9/xgv+6i9KOxYS2amV/VEQqyWn GZy+o4bYvnTxMd661wOdeBefY5tts9i/dhZC+/Z79Pl+DLciOYZGc5pvEr/IVSICaJGc nGhw== X-Gm-Message-State: ACgBeo1i38G7MXfnepCHea5PqdrO+7/7SuZt4ptlrjLUYrZhhesFBqOx SUtvdq22xO2yX+McSJCIK+GY2g== X-Google-Smtp-Source: AA6agR58AU5/fcjhX9HiMoCrU9x/aSQJPJMasnfDN1/9TmHqLG5XxGMpwRyfIf05HzWat0V+XB97gw== X-Received: by 2002:ae9:df01:0:b0:6bb:4e95:6a59 with SMTP id t1-20020ae9df01000000b006bb4e956a59mr13111817qkf.339.1662812470054; Sat, 10 Sep 2022 05:21:10 -0700 (PDT) Received: from ahch-to ([201.183.1.162]) by smtp.gmail.com with ESMTPSA id w4-20020ac87e84000000b0035ba7012724sm1470761qtj.70.2022.09.10.05.21.09 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sat, 10 Sep 2022 05:21:09 -0700 (PDT) Date: Sat, 10 Sep 2022 07:21:06 -0500 From: Jaime Casanova To: =?iso-8859-1?Q?Mois=E9s_Lim=F3n?= Cc: pgsql-bugs@lists.postgresql.org Subject: Re: Bug in UPDATE statement Message-ID: References: <038F1E06-4866-4563-8DE0-229B8B19ABD2.ref@yahoo.com> <038F1E06-4866-4563-8DE0-229B8B19ABD2@yahoo.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <038F1E06-4866-4563-8DE0-229B8B19ABD2@yahoo.com> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Sat, Sep 10, 2022 at 01:44:40AM -0500, Moisés Limón wrote: > Hello, > > PostgreSQL 14.4 compiled by Visual C++ build 1914, 64 bit > > A bug was found in the UPDATE statement when the WHERE condition hasn't valid fields and only one valid field, the changes are applied for all rows. > Error detected using a Function with an UPDATE statement. > > Moisés Limón Ruiz Hi Moisés, Can you give a complete example of what you are describing (at least a create table command, insert some rows and an UPDATE with the behaviour you describe). -- Jaime Casanova Director de Servicios Profesionales SystemGuards - Consultores de PostgreSQL