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 1sVFem-008qtq-A7 for pgsql-general@arkaria.postgresql.org; Sat, 20 Jul 2024 19:22:12 +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 1sVFei-001Smp-PG for pgsql-general@arkaria.postgresql.org; Sat, 20 Jul 2024 19:22:09 +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 1sVFei-001Smg-Do for pgsql-general@lists.postgresql.org; Sat, 20 Jul 2024 19:22:08 +0000 Received: from mail-wr1-x436.google.com ([2a00:1450:4864:20::436]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1sVFeh-000b2T-Ag for pgsql-general@lists.postgresql.org; Sat, 20 Jul 2024 19:22:08 +0000 Received: by mail-wr1-x436.google.com with SMTP id ffacd0b85a97d-36865a516f1so1862723f8f.0 for ; Sat, 20 Jul 2024 12:22:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1721503325; x=1722108125; darn=lists.postgresql.org; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=yIH1kk+5EPEse9iGemX4dDXuUL6PibTzSfa6APL1ICk=; b=AL2Jo6F0KDDVLtFKCWzNPcuxI/CL/OxCN9fd9xRHqVUqRvaPTpMSv12lxWJGUsk3RI yUrBHbBa00qI0+D44yKfJOMp4fCFNhsdfmGPqIRZUQE2ipHNJLtFvfzLwFhtG2V0hG/C Oy7uAtMadAbSENJHJvveoCetul+hWU+/haXuTBaGoD55mBwLcmd8FwhCv1Vh2uW07J+n J3F25FTuY+4fBW3v5+33MUpamr0Y6Nk5crY3rfzzYNuSJR/QXjXydK1Bx2JRNB6yMD5j 3ds2OhB42dVMQkYT1GKwi4DIw82o7wC1wIZgtea4LVi29GFt/sqzXi75+XnXGr69Xf5P B5Xw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1721503325; x=1722108125; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=yIH1kk+5EPEse9iGemX4dDXuUL6PibTzSfa6APL1ICk=; b=lPePRUATS+Imvdp058Nv+kfT5RQXRWCnY2HaK2DS9iqoTjPR6cD+igVvH2NjMKEPDr ftt7d1jd3ixiv2QB9MphWc8/H4j1SP6OA0WYbxtWGRkvwJcvTxImYfn8HRV/ezhsCkBP 8Q/ZSyTJeoxapRWeit5KhpIECZAX2Bu9K3pMXJJk50tyEixmJzsq10nwyV75azbIVTM8 e/Cxyd1GrVDE8Pg2wNFq5jVYwK268y2MMppAl4o6aRtu91VUdidvlsI393RidLsE9Tgb VbHZH+10HxHkWLZ6cOlobr//H6PB815UL6MZBjSHLLsWRbVykQTod4B9zexoAxpz8EYo jG+w== X-Gm-Message-State: AOJu0YyRlHD+RrvUeDABD/9rxLuR0bA1Wb86ru7thiM2IFXMA5YcGeT4 4YVUUhhyN+nSHfOjcOC+VnTsSET0ycjV60hdpU9xMVmQh05moQBVcbkhmxA02GiJo4OwK7zNA5b Bi/5th8xW9cSBnVdFNQ3q91EVPIY= X-Google-Smtp-Source: AGHT+IHcM7SY9Guas2cjfSU2yJLXOhemetoGwxmR1WlR+ZjAA4+5RHA94DLUB0uuR26hvlg7KEIIQe46kxSjvT33JvQ= X-Received: by 2002:adf:f947:0:b0:368:6596:edba with SMTP id ffacd0b85a97d-369bae67475mr1529533f8f.39.1721503324440; Sat, 20 Jul 2024 12:22:04 -0700 (PDT) MIME-Version: 1.0 References: <937562047.1752859.1721295502145.ref@mail.yahoo.com> <937562047.1752859.1721295502145@mail.yahoo.com> In-Reply-To: <937562047.1752859.1721295502145@mail.yahoo.com> From: Michael Nolan Date: Sat, 20 Jul 2024 14:21:56 -0500 Message-ID: Subject: Re: Re. Select with where condition times out To: "sivapostgres@yahoo.com" Cc: Postgresql General Group Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Thu, Jul 18, 2024 at 4:38=E2=80=AFAM sivapostgres@yahoo.com wrote: > > Hello, > PG V11 > > Select count(*) from table1 > Returns 10456432 > > Select field1, field2 from table1 where field3> '2024-07-18 12:00:00' > Times out > > The above query was working fine for the past 2 years. > > Backup was taken a day back. Need to recover complete data as far as pos= sible. > > Any possible way(s) to do this? > > BKR Sivaprakash > If you do a full backup, does it complete in a normal manner and the usual = time? Have you tried doing a shutdown and restart of the database, or possibly rebooting the server? You may need to alter the database server settings to increase the maximum query time. Mike Nolan htfoot@gmail.com