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 1rQkjQ-003Lkw-50 for pgsql-bugs@arkaria.postgresql.org; Fri, 19 Jan 2024 09:00:08 +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 1rQkjP-008EuE-3k for pgsql-bugs@arkaria.postgresql.org; Fri, 19 Jan 2024 09:00:07 +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 1rQkjO-008Eu5-Ps for pgsql-bugs@lists.postgresql.org; Fri, 19 Jan 2024 09:00:06 +0000 Received: from mail-lf1-x133.google.com ([2a00:1450:4864:20::133]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1rQkjM-002buH-F2 for pgsql-bugs@lists.postgresql.org; Fri, 19 Jan 2024 09:00:06 +0000 Received: by mail-lf1-x133.google.com with SMTP id 2adb3069b0e04-50e7abe4be4so640051e87.2 for ; Fri, 19 Jan 2024 01:00:04 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1705654803; x=1706259603; darn=lists.postgresql.org; h=in-reply-to:from:references:cc:to:content-language:subject :user-agent:mime-version:date:message-id:from:to:cc:subject:date :message-id:reply-to; bh=fwynUeUjcVgS1qIlXZ3Geci39aXQp7t42vTnFHA3KAk=; b=g1HnCPuqgXVDpIOgdwg7r1ufXcn9++M1pDfKHgb6AZOqdU/KJUtUUDhZowkasljZzZ FjCxNjbQDK0Aex/4XAFF8EZgRPSEnD53k2J0aClSJ1CNS7QywRExxcuAuPdmnxphwwGE NK36JlFCCx8S5lyoetP+4QeNd30ak166XPK9/DSY5mbCG/9pNBm7NaerWJ4U7rGEZXzG GclZxD3p8raoQvMJlqaEjkmCsa87ZPOUVkF2o3cByV1EVSf04W8sk1l03sokoNiJGaLw 2cigMn4NXNYxHISAl8V3/0wz4Fb9CcgxxRqGsAPlct+RlbNCqYDHJnZ0O31azGQXTsKc Tc8A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1705654803; x=1706259603; h=in-reply-to:from:references:cc: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=fwynUeUjcVgS1qIlXZ3Geci39aXQp7t42vTnFHA3KAk=; b=JbcWKvgYOP85bJesLxWTOJmNMi7jKDnkOThW1MfvqT4olFT7BwksUnS1I9YoNuqSQE hV/WVe68GD/fgBXplQewB5EcPmbnO9oUNBDixnlmnSQQ9hNjcHotBv+w4hkM4I07iI3U Rc8omnR12rfPXNLF28jRTGaAxbwgjDvDN/MoXXygfbhOmcy1fi91r+0xcbxCissU2N2w Cob7oUrDYnZli2emNYGaeW7byMjiqJaDVF7g35IHjn8a0UmwEeu6clmwR8xP8A4CRVvw maXVqa0+nZhJMH7WqoFBhJ4/aQqeM3a+teTmnQ6gzoJ+kiZSsROtJjta2Bt7+bD88DW1 Fu/w== X-Gm-Message-State: AOJu0YylyfoGjcVwjlPK5GVCoJjknECP1u65DIh1UcxWDTSkf7FmflN0 3ZxSKjmPexbpTXYX1zcCflVkuHZI4piHIyw66ywzJd8tDYWCc6Ch X-Google-Smtp-Source: AGHT+IHYomXXgQz3Pai56cl0699J1eeioui5n7VGbpjbQdYMl/N4Toxvq74ISyEcidv8Aph15h0INQ== X-Received: by 2002:a05:6512:52f:b0:50e:aed5:ec06 with SMTP id o15-20020a056512052f00b0050eaed5ec06mr508205lfc.87.1705654803212; Fri, 19 Jan 2024 01:00:03 -0800 (PST) Received: from [1.0.0.7] ([91.185.77.50]) by smtp.gmail.com with ESMTPSA id m15-20020ac24acf000000b0050f0a0f27d4sm908605lfp.220.2024.01.19.01.00.01 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 19 Jan 2024 01:00:02 -0800 (PST) Content-Type: multipart/alternative; boundary="------------8zeELpGmq4NT1iSZcmNK6KTP" Message-ID: <9481c16e-8477-eb73-4e20-91bb1a13e2e0@gmail.com> Date: Fri, 19 Jan 2024 12:00:00 +0300 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.4.2 Subject: Re: BUG #18297: Error when adding a column to a parent table with complex inheritance Content-Language: en-US To: Tender Wang Cc: Richard Guo , pgsql-bugs@lists.postgresql.org References: <18297-b04cd83a55b51e35@postgresql.org> <38de09cc-70f3-28ee-fe67-ae13cba23e61@gmail.com> From: Alexander Lakhin In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk This is a multi-part message in MIME format. --------------8zeELpGmq4NT1iSZcmNK6KTP Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit 18.01.2024 18:42, Tender Wang wrote: > > I think we can sort the role_addresses list and skip the same role id. I don't intend to fix above two issues in one > patch. > So I add a new 0001 attached patch. > > > Perhaps, you would like to fix it in passing too. I've rechecked all the > other object types, that can be DROPped with a list (namely, AGGREGATE, > DOMAIN, EXTENSION, FOREIGN DATA WRAPPER, FOREIGN TABLE, FUNCTION, INDEX, > MATERIALIZED VIEW, OPERATOR, PROCEDURE, ROUTINE, SEQUENCE, SERVER, > STATISTICS, TABLE, TYPE, VIEW), and found that all of these handle > such duplicate entries with no error. > > > I'm not sure if there are other problems like this. > Yes, I've encountered a similar issue, this time with ALTER (TEXT SEARCH CONFIGURATION): CREATE TEXT SEARCH CONFIGURATION ispell_tst (COPY=english); CREATE TEXT SEARCH DICTIONARY ispell (Template=ispell, DictFile=ispell_sample, AffFile=ispell_sample); ALTER TEXT SEARCH CONFIGURATION ispell_tst ALTER MAPPING FOR word, word WITH ispell; ERROR:  tuple already updated by self And again, I could not get similar errors with all the other ALTER commands, that accept lists. Sorry for mixing two different problems together, I should have reported it separately. Best regards, Alexander --------------8zeELpGmq4NT1iSZcmNK6KTP Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit
18.01.2024 18:42, Tender Wang wrote:


I think we can sort the role_addresses list and skip the same role id. I don't intend to fix above two issues in one patch.
So I add a new 0001 attached patch.


Perhaps, you would like to fix it in passing too. I've rechecked all the
other object types, that can be DROPped with a list (namely, AGGREGATE,
DOMAIN, EXTENSION, FOREIGN DATA WRAPPER, FOREIGN TABLE, FUNCTION, INDEX,
MATERIALIZED VIEW, OPERATOR, PROCEDURE, ROUTINE, SEQUENCE, SERVER,
STATISTICS, TABLE, TYPE, VIEW), and found that all of these handle
such duplicate entries with no error.

I'm not sure if there are other problems like this.


Yes, I've encountered a similar issue, this time with ALTER (TEXT SEARCH
CONFIGURATION):
CREATE TEXT SEARCH CONFIGURATION ispell_tst (COPY=english);
CREATE TEXT SEARCH DICTIONARY ispell (Template=ispell, DictFile=ispell_sample, AffFile=ispell_sample);
ALTER TEXT SEARCH CONFIGURATION ispell_tst ALTER MAPPING FOR word, word WITH ispell;
ERROR:  tuple already updated by self

And again, I could not get similar errors with all the other ALTER commands,
that accept lists.

Sorry for mixing two different problems together, I should have reported it
separately.

Best regards,
Alexander
--------------8zeELpGmq4NT1iSZcmNK6KTP--