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 1lCm71-0000cR-MQ for pgsql-admin@arkaria.postgresql.org; Thu, 18 Feb 2021 16:25:07 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1lCm70-00072y-Iz for pgsql-admin@arkaria.postgresql.org; Thu, 18 Feb 2021 16:25:06 +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 1lCm70-00072q-92 for pgsql-admin@lists.postgresql.org; Thu, 18 Feb 2021 16:25:06 +0000 Received: from mail-qv1-xf35.google.com ([2607:f8b0:4864:20::f35]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1lCm6x-0000uY-5X for pgsql-admin@lists.postgresql.org; Thu, 18 Feb 2021 16:25:05 +0000 Received: by mail-qv1-xf35.google.com with SMTP id 2so1197801qvd.0 for ; Thu, 18 Feb 2021 08:25:02 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=content-transfer-encoding:from:mime-version:date:subject:message-id :to; bh=+N4wUa+kvgW1ofUj6kugkXaOjx4U7SMBZV7GaGubPyE=; b=FHNP9P6eI3dPHDbGXEeAeIuTyz0oyALJugIsGv16hJLqCiT54+LdV6Ib0N/Vcesd/U d/AV9ar7LaeHe+3ObbmLHGp7TxqU9cpP4NiD6JZ8/wPscbdqdE7/WYkdyCG+n+xwbsVb XQtM0X7tAsQMpYfBlW7PDqB8IweowBMgTQIC7DpMbVo55EfdWsLzG0GY3a7n32qqediu 6+EhvnrG3jmVH6JvG34OyOZXbzw9kMUGu+D9X0q5mKCael7AvCeEhZwN+mDfjGDWhJqU PZWjn1VlHtjtUywa6bS2VS1ymlFruQ0iTWGC7QLEi9IfUPR0ZX4IhZQKY/RwsqtbhGLZ bR4Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:content-transfer-encoding:from:mime-version:date :subject:message-id:to; bh=+N4wUa+kvgW1ofUj6kugkXaOjx4U7SMBZV7GaGubPyE=; b=HLlMr9t+MeregeGuHg7XxO9dgWqOUAK3a+P9Y1J7dPvibtR3dbuKefBPCS+JeOCNsJ 6t2i++r6/chO9AfGGJaXN3jH+p9SPR6bCH3gjWIgWbhx3DaaBFjNfSdfUlG4fh8Dzh1f PDhMFnAbkXFD9jWYeAphGlaMYztRFQGLXHU0KEME+QLv0zxlWcXTQLYVLqDvnOmWQVDb QKarQccDgrEvUx9l0McYrPCIuHill42K7vKTwGNcl5w2XLLHEVBFtzhRFF3SnIrpqC51 gzFNFkK4hwTIh5dT/G0RkmWXTGYAjbXoqtJKrfZ3BF5EBvLgSjT4xFgk89WTfMPgKuPZ cfWA== X-Gm-Message-State: AOAM532bZzSwlkKYvRE0hBR8gwW7oKcgUSkTKe/rNxplYZJvv0YIJAtf kB82H+swcC2kg0i8km2oz5aHbCfcLUyoMQ== X-Google-Smtp-Source: ABdhPJz9glTloMpU/Uxy6We1raPODJ3z1sgiYjbMthRtDIDUZbsmnOqi+JghHl+T7kp2y0GORgHbeQ== X-Received: by 2002:a0c:abce:: with SMTP id k14mr4679825qvb.23.1613665501596; Thu, 18 Feb 2021 08:25:01 -0800 (PST) Received: from [192.168.254.67] (h178.165.133.40.static.ip.windstream.net. [40.133.165.178]) by smtp.gmail.com with ESMTPSA id l6sm4272208qki.25.2021.02.18.08.25.01 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 18 Feb 2021 08:25:01 -0800 (PST) Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable From: John Scalia Mime-Version: 1.0 (1.0) Date: Thu, 18 Feb 2021 11:24:57 -0500 Subject: Disabling indexes on a table Message-Id: <8D9636C9-D38E-4857-A542-1469A11A25FF@gmail.com> To: Pgsql-admin X-Mailer: iPad Mail (18D52) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk One of my developers asked me about this, and he suggested running the follo= wing update: UPDATE pg_index SET indisready=3Dfalse WHERE indrelid =3D (select oid from pg_class where release =3D =E2=80=98his_= table=E2=80=99); I told him it=E2=80=99s never a good idea to update anything in a system cat= alog by hand, but that I would reach out here for a better opinion. Am I cor= rect that he shouldn=E2=80=99t try this, or is he OK to do this? His table h= as approximately 8 different indexes on it, and those really slow down his b= ulk loads. Usually when I have to get involved, I just drop his indexes and r= ebuild them afterwards, and I know that is always safe. =E2=80=94 Jay Sent from my iPad=