X-Original-To: pgsql-admin-postgresql.org@postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id AD7E99FA040 for ; Mon, 17 Jul 2006 15:44:56 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 47877-04 for ; Mon, 17 Jul 2006 15:44:51 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id B4CE79F9F73 for ; Mon, 17 Jul 2006 15:44:50 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.6/8.13.6) with ESMTP id k6HIhUH3004955; Mon, 17 Jul 2006 14:43:30 -0400 (EDT) To: "Mr. Dan" cc: pgsql-admin@postgresql.org Subject: Re: On-line backup In-reply-to: References: Comments: In-reply-to "Mr. Dan" message dated "Mon, 17 Jul 2006 14:21:27 -0400" Date: Mon, 17 Jul 2006 14:43:30 -0400 Message-ID: <4954.1153161810@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200607/148 X-Sequence-Number: 22394 "Mr. Dan" writes: > ... What happens is that we have a 'hot' table (one with many many > transactions) that gets inserted and deleted often. About once a month now > when we do a select from that table the results of the select do not match > the where clause, ex. > select * from recent_projects > where user_id = 139 > sometimes produces these results: > user_id project_id > 139 3 > 139 1 > 139 17 > 754 11 Hmmm .... that looks sorta familiar. What is the query plan that's used for this SELECT? regards, tom lane