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 1pLVR8-0001bn-TG for pgsql-general@arkaria.postgresql.org; Fri, 27 Jan 2023 20:35:03 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pLVR7-0000F2-Cg for pgsql-general@arkaria.postgresql.org; Fri, 27 Jan 2023 20:35:01 +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 1pLVR5-0000Ei-O7 for pgsql-general@lists.postgresql.org; Fri, 27 Jan 2023 20:35:01 +0000 Received: from wout5-smtp.messagingengine.com ([64.147.123.21]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pLVR2-0001oW-39 for pgsql-general@lists.postgresql.org; Fri, 27 Jan 2023 20:34:58 +0000 Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.west.internal (Postfix) with ESMTP id DE3CB320090C; Fri, 27 Jan 2023 15:34:53 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute5.internal (MEProxy); Fri, 27 Jan 2023 15:34:54 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aklaver.com; h= cc:content-transfer-encoding:content-type:date:date:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:sender:subject:subject:to:to; s=fm2; t=1674851693; x= 1674938093; bh=JeUIU1G/BYijCNruG1FjkhVrnHg6pOSnvDG7Ob9Fp/A=; b=f 3wHWuKI7GUBs5ldIVodycAIc9bFgcs2z8UIf60Vy58oVZsw3au3SJISFa2WvfpaY DvpUsmdFJ7BZo5MATdV4xoP3rQYEShdOXcgM5OC77ExC/x1lRK50IRGQEUoZhZPN BIpB8Ui63bgsj3lxoVs+NlwpHuEh9p16XGxQGppIHOT2etAB9Al3yUD3pgeiJtmu enLyW8/NsKfBkyVhwndzJYvLxXI0Hd5KPF1mvq9ibLb3kbPWT9HOo0kEI6ww75Wt Q1uqV+cbMRBi030PQ/euLb9k9laxV6l+44sLH34+bRsEzbbrfYhua2hWQi9NOPWa VnhZxIlPrp1n7P7hFA6fQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:date:feedback-id:feedback-id:from:from:in-reply-to :in-reply-to:message-id:mime-version:references:reply-to:sender :subject:subject:to:to:x-me-proxy:x-me-proxy:x-me-sender :x-me-sender:x-sasl-enc; s=fm3; t=1674851693; x=1674938093; bh=J eUIU1G/BYijCNruG1FjkhVrnHg6pOSnvDG7Ob9Fp/A=; b=nxplZSBB9CNn0OtOb 9qo4pqkuVVnGv7Jmk4VJ9GTFAN6fE27zpLGLU9njUVcgXxw5lC/5LjA2S6gqgo/u K0uIje1Vdrke+lbGe2zSqa0SBkE5mm1sNrEJOhOKy4ZzrU5cgiYrIQMogT9fnOnH RlCdg/IHA23zfvDVFhVFJw92WBAUySEX+V31cXAx1wm/tIGq7IrDmD5SoZEOj1tq LkQg6xEetIwCsZxYSFf0J79wUN3S/bqys5OiIQluoIqNtPCL7uAC99Vcr0DQSZHR 5qF52wEJw0I4H69CyhFWDxfVhsqxQUuh2Y48eBDOAIb1KQ5Yi1F/ejwzDmjeftw1 vs2Mg== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedruddviedgudefkecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmd enucfjughrpefkffggfgfuvfhfhfgjtgfgsehtjeertddtfeejnecuhfhrohhmpeetughr ihgrnhcumfhlrghvvghruceorggurhhirghnrdhklhgrvhgvrhesrghklhgrvhgvrhdrtg homheqnecuggftrfgrthhtvghrnhepvedvkeeihfduhffhtdekleegffduiefgteejgeff gffhteefleeludfgleelgeevnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpe hmrghilhhfrhhomheprggurhhirghnrdhklhgrvhgvrhesrghklhgrvhgvrhdrtghomh X-ME-Proxy: Feedback-ID: i76984098:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Fri, 27 Jan 2023 15:34:52 -0500 (EST) Message-ID: <27ccec91-9ff2-b566-efb1-e1c552563514@aklaver.com> Date: Fri, 27 Jan 2023 12:34:52 -0800 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.6.1 Subject: Re: Indexes mysteriously change to LOG To: Rumpi Gravenstein , PostgreSQL References: Content-Language: en-US From: Adrian Klaver In-Reply-To: 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 1/27/23 12:23, Rumpi Gravenstein wrote: > We are on PostgreSQL 14.5 on x86_64-pc-linux-gnu, compiled by gcc (GCC) > 8.5.0 20210514 (Red Hat 8.5.0-10), 64-bitPostgreSQL 14.5 on > x86_64-pc-linux-gnu, compiled by gcc (GCC) 8.5.0 20210514 (Red Hat > 8.5.0-10), 64-bit > > We have recently discovered that on some of our partitioned tables > indexes that were created as: > > CREATE UNIQUE INDEX chapter_u01 USING btree (dur_uk, catalog_id) How did you do the above without the table name? > > somehow changed to include the ON ONLY option: > > CREATE UNIQUE INDEX chapter_u01 *ON ONLY *chapter USING btree (dur_uk, > catalog_id) > > There is no SQL issued that explicitly requests this "ON ONLY" option. > I am wondering if this is a side-effect of some other activity. > Googling and looking through documentation haven't helped. > > Does anyone have any thoughts on how this might happen? > > -- > Rumpi Gravenstein -- Adrian Klaver adrian.klaver@aklaver.com