Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.92) (envelope-from ) id 1j743e-0004dk-8w for pgsql-admin@arkaria.postgresql.org; Wed, 26 Feb 2020 21:17:30 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1j743c-0003Kt-RI for pgsql-admin@arkaria.postgresql.org; Wed, 26 Feb 2020 21:17:28 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1j743c-0003J7-F9 for pgsql-admin@lists.postgresql.org; Wed, 26 Feb 2020 21:17:28 +0000 Received: from mail-vs1-xe36.google.com ([2607:f8b0:4864:20::e36]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1j743Z-000409-Vp for pgsql-admin@lists.postgresql.org; Wed, 26 Feb 2020 21:17:27 +0000 Received: by mail-vs1-xe36.google.com with SMTP id n27so429128vsa.0 for ; Wed, 26 Feb 2020 13:17:25 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=to:from:subject:message-id:date:user-agent:mime-version :content-transfer-encoding:content-language; bh=+yi47eYBpQfWpGXltul+BibIZ+vGTJXYRxo8+QFhpLY=; b=ScPsQr9bUS4EFzNcIV4orxwKxVsi5rr6GFWrZCyAkLnLzSZiZWIORyEGLeBixDRLId iIZoHsXD5rtN5Xq4MsSdkpnDaHuvbQK5Ke3EluRN0iGx/bQGOUFZ4beJo69sJIh/z7TW B2/60Xu/siiSbGzmTn/I6HZdKQp1YB+knCJC2cyTcwq2eKTRfqqekzhvV4DLam0FAzH3 11pPzxjc69odb5D/X7zYNmZXedaMcCHNsNoP0Qigzh8jJ0rxMpGFuOxYIyU/mNQqaWMF X0zOkhvF+8Rke3qUKdPflBxAkByP5i6dhJ+S+SIPwDEANrWytl1baVSOmCX70CRRhT0d an6Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:to:from:subject:message-id:date:user-agent :mime-version:content-transfer-encoding:content-language; bh=+yi47eYBpQfWpGXltul+BibIZ+vGTJXYRxo8+QFhpLY=; b=qSQpN2hg/0nnuWEmHJfF5dhe/S7QWvukcANyAbfNKOviUvMjxMvg77zcDXDd0tT+5u h5GIPJ1BAN0q9/jydfsqjpGH828y4SIhKuxHl9zU2rzD5ZTzRGcOJzZQN03vown4dkht jJKlVRaiOu0ofAb9lrfDDFnHq5MZw2eoO/pyTDAW9Hj8XWW2QzMeE8GEB/aOV+j/hn34 0aj7Iu9DyXO79u0jMHHIRMrdIFz4PNuVMLp4nlaWsN5ZwhoADjv4GrHNEBLcpThst4Tz VTXzFY4V7qVJVGJDXUneFWzdwh5ThJTqmqgbEYh48zd73j2tPs+zUcQ7MQlX29ZMYdsI fwVQ== X-Gm-Message-State: APjAAAWudpr/vnRtMeit6IB9+Rv5QN0h8z1faaNFJ2B2lcZvSAK5SIOk AfwbVX37qAtDOigYxBPMXtF6Y1/j X-Google-Smtp-Source: APXvYqzTnXxd2ygGxLXvKK59Av52nVoDV7O1PMYIPQ6Pd7tN849LtOaFm4SYAqo8qfWBIv2Exy6pIQ== X-Received: by 2002:a67:be13:: with SMTP id x19mr658324vsq.20.1582751843754; Wed, 26 Feb 2020 13:17:23 -0800 (PST) Received: from dev.beauqueue.com (c-65-34-174-126.hsd1.fl.comcast.net. [65.34.174.126]) by smtp.gmail.com with ESMTPSA id s123sm1408628vka.27.2020.02.26.13.17.23 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 26 Feb 2020 13:17:23 -0800 (PST) To: pgsql-admin@lists.postgresql.org From: Jacque Subject: "NEVER" cautioned to auto_explain's log_analyze parameter on Production Message-ID: Date: Wed, 26 Feb 2020 16:17:21 -0500 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.3.1 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk I've seen it said to "NEVER" apply auto_explain's log_analyze parameter on Production.    I get the general foreboding doom that can be beset by a highly looping control structure eating up disk space (with no indication of its exit condition time) but is genrous-disk-writes  pretty much the only reason for avoiding this in folk's opinion?    And say a well-mannered connection using it could be safe  in production?    Seems to be afterall what the pganalyze folks must be  doing with their commercial product afterall.