Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1eXsS2-0001Z6-3f for pgsql-admin@arkaria.postgresql.org; Sat, 06 Jan 2018 17:40:10 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1eXsS1-000329-CH for pgsql-admin@arkaria.postgresql.org; Sat, 06 Jan 2018 17:40:09 +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_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1eXsRz-00030j-Nz; Sat, 06 Jan 2018 17:40:09 +0000 Received: from out2-smtp.messagingengine.com ([66.111.4.26]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1eXsRu-0005xk-TO; Sat, 06 Jan 2018 17:40:07 +0000 Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id E9F4720961; Sat, 6 Jan 2018 12:40:00 -0500 (EST) Received: from frontend1 ([10.202.2.160]) by compute6.internal (MEProxy); Sat, 06 Jan 2018 12:40:00 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aklaver.com; h= content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm1; bh=jbQyUA+vAarbdxXcyEx10g0ueaAkn 3SxE+rQVbXu5uk=; b=PpAy7SeiK1WwS7wJ5+UeepITcO4gsAo9H/hNe80C3575I V5f0mA5LEPsFMil4Nacx3Whx7XaMsq5GGdDC2zD1O1l4cb/1gmvu3TiiN8LniSve GNX90Kbg6rG9Kyl2tOCBBBj7TV/kUq6WMTnKWGdPmux0xr+SEHLt0ybXtLCEruOj hBlY1M2KKoy7YKOMtVXenpPddE1O4xXtHNmhrbUBCKC7QJ6hMpmlJgJjXTq6X9h3 ZXGPh7Ou5Z4PIr1WVeMgaqgKCENto07EFVt/2VYCT/1LaO234n6wMhObtRPPUiVD IZIOEqd+J3j0cvGRkulFV7k8HEELNkJsCt63MpKbw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=jbQyUA +vAarbdxXcyEx10g0ueaAkn3SxE+rQVbXu5uk=; b=jUzRQMWj/VamUCMXOx7v8R QXegV7o2okNvleOmUDVSCjUAGE6JCb7KkJ9hpVW0L625hfEif2Zwr1MNXHfzjANQ +YDnrzBRNaJRJI3hxHuLjLAh4JkSqQA7TTnXuPMW02100DIpCqR+OeyrCWhzLn8Q 5gZqYRAkfCiy+j5fPXtCu+QwNuW7o2I32kmw2kX4hUppKDcG8qY+TfuDKBOlj40J mcQOq/4TDMIs7JpbwnQZVhZNqFEGYrcho0AY4h/ol+hbbZR59TMcvNYg/8PMDk5F wKjVqfTycTIzzQFQ08xJZgh5ZZCcx37shxuBMTGfH8rcQPM99jTMtBxXZkpgTNtA == X-ME-Sender: Received: from [192.168.1.3] (unknown [67.40.177.89]) by mail.messagingengine.com (Postfix) with ESMTPA id 530E87E1A2; Sat, 6 Jan 2018 12:40:00 -0500 (EST) Subject: Re: Ideas to deal with table corruption To: Luis Marin , pgsql-admin@postgresql.org, pgsql-general@postgresql.org References: From: Adrian Klaver Message-ID: Date: Sat, 6 Jan 2018 09:39:59 -0800 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On 01/06/2018 02:11 AM, Luis Marin wrote: > > Dear community, > > I am looking for ideas, to help me, check what is happening with a > possibleĀ  table corruption, IĀ  have some FK that works ok, but some stay > in the state waiting forever, however selecting the same table works fine. From further comments below I think you are talking about creating a FK on a table, is that correct? If not, what are you trying to do? The table schema and code showing your process would be helpful. And yes tailing the Postgres log file during the above could be helpful. > > Since, I am a newbie, in PostgreSQL, what should be my firsts steps, in > order to have an idea how to fix this problem. > > I am thinking in watching my postgresql log error file during the > requests for creating our FK, > What do you suggest me > > Centos 7.2 > Postgresql 9.4 > > Thanks -- Adrian Klaver adrian.klaver@aklaver.com