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 1pX4cp-0004Om-Ol for pgsql-general@arkaria.postgresql.org; Tue, 28 Feb 2023 18:22:55 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pX4co-0006Dy-FT for pgsql-general@arkaria.postgresql.org; Tue, 28 Feb 2023 18:22:54 +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 1pX4co-00069o-2Q for pgsql-general@lists.postgresql.org; Tue, 28 Feb 2023 18:22:54 +0000 Received: from mail-qt1-x82f.google.com ([2607:f8b0:4864:20::82f]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1pX4cj-0003IW-IH for pgsql-general@lists.postgresql.org; Tue, 28 Feb 2023 18:22:52 +0000 Received: by mail-qt1-x82f.google.com with SMTP id h19so11564336qtk.7 for ; Tue, 28 Feb 2023 10:22:49 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=content-transfer-encoding:in-reply-to:from:references:to :content-language:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date:message-id:reply-to; bh=pJD7hiwJbJIDDlK87Xk5x+eVYAsemasLSAKX6Qua1zY=; b=EpVk6pnt7mNwgCuGJFLZ50JIjodld/Tvcp3kJvRq+GkBFtV/aTT4GRkvq+xe1jiQNI HqriZPtdxrj9xJ2sg1DG9y4IrU8f4/YAS5njrHEvX+ljv8RCNmp5W9vTHTDEh12IY16V wl5d1qBC52/mBlfUoSyT0y/VV9Dta9YpJ2BzDAFWUJoGsQGMZg06WFIwvQ+l+cjpaoB9 BDDnA8auPx87TDQZOpricGEaxRm6GhRLx9ZMFbwUrZYrPvVA3PMx/5LGlrqlOYW3ptBf TAZlvySpmZEo0s5omhMobxf/TAn66HyqWOE4Rg9NQd2VBUDcKlNQHwp5DuTUmqZi7HcI p6lg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:in-reply-to:from:references: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=pJD7hiwJbJIDDlK87Xk5x+eVYAsemasLSAKX6Qua1zY=; b=o3A10hWX8RLsR5SD63o2MV8D+Yw1qFkf8NIcMtk5gU41HRMc6m585kx2Mv1prGVpTq NmLkVJTBEK/lqLwdqy9WeCKHVIIAhWjZ/63uLnVX626yPBNCcmiHIBZo+7nznHhaYdat LhZVjk1kGlIddbegQTTJ3J+dofy2mzWSyv3hC87foBnZmF4HJALpTfZzT8aA+LcfVhu7 lIgWT7atsyQsey8rlGqa0KNCMVu+8pvmKcr2QAR+kzg6lvTpFvd5sxOG9MZEQ6w5jWn/ ix5wJ3DbXAt+POOg3hu/jwBcUKQMWMIpioTDeoYAPcxpQAlczcaAjURe/qyxFHKQsEex Vv4Q== X-Gm-Message-State: AO0yUKVW2aYGH5wWgbHTe9oHSbbl23CNt1O8SQV/9Yh1nycL6DPuYvSw Pus5WnvpLFn10c6LioHNGzjByrhm+7E= X-Google-Smtp-Source: AK7set9x1TZQiWwoUZ2kRKM+IvQds2iRsOXVH4qdoi82tHgAQ9yhQuBfr/knokfDmLyrrpATwrtMtw== X-Received: by 2002:a05:622a:1aa0:b0:3bf:e4da:2367 with SMTP id s32-20020a05622a1aa000b003bfe4da2367mr6729866qtc.3.1677608568326; Tue, 28 Feb 2023 10:22:48 -0800 (PST) Received: from ?IPV6:2600:1700:bd2c:b810::43? ([2600:1700:bd2c:b810::43]) by smtp.googlemail.com with ESMTPSA id h9-20020ac85489000000b003b62e9c82ebsm6879655qtq.48.2023.02.28.10.22.47 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 28 Feb 2023 10:22:47 -0800 (PST) Message-ID: Date: Tue, 28 Feb 2023 12:22:47 -0600 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.4.2 Subject: Re: Quit currently running query Content-Language: en-US To: pgsql-general@lists.postgresql.org References: <20230228173145.hkyrsoqicyyjg7bx@hjp.at> From: Ron In-Reply-To: <20230228173145.hkyrsoqicyyjg7bx@hjp.at> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 2/28/23 11:31, Peter J. Holzer wrote: > On 2023-02-28 07:42:08 -0600, Ron wrote: >> On 2/28/23 04:53, Albert Cornelius wrote: >> >> How can I quit a currently running query? I've issued a query and >> my server does not respond anymore. Is there another solution than >> using kill -9? >> >> >> What specifically do you mean by "my server does not respond >> anymore"?  Because if "the server" really doesn't respond anymore, you >> can't even issue "kill -9". > The term "server" can mean different things: > > 1) A role in an interaction between two programs. The "client" is the one > which issues requests, and the "server" is the one which fullfills > them. > > 2) A program which is intended for the server role. Note that a program > can be a server for one protocol and a client for another (e.g., a > database server can be a DNS or LDAP client). (And some programs are > even server and client for the same protocol) > > 3) A machine intended for running server programs. > > You are thinking of the 3rd meaning. My guess is that Albert meant the > first. And maybe he's referring to his client software... That's why I asked him for clarification. -- Born in Arizona, moved to Babylonia.