Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1XPGBw-0006f0-Ip for pgsql-general@arkaria.postgresql.org; Wed, 03 Sep 2014 19:26:05 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1XPGBv-0005tc-El for pgsql-general@arkaria.postgresql.org; Wed, 03 Sep 2014 19:26:03 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1XPGBk-0005cM-V9 for pgsql-general@postgresql.org; Wed, 03 Sep 2014 19:25:53 +0000 Received: from out1-smtp.messagingengine.com ([66.111.4.25]) by makus.postgresql.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1XPGBe-0000i1-UX for pgsql-general@postgresql.org; Wed, 03 Sep 2014 19:25:49 +0000 Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by gateway2.nyi.internal (Postfix) with ESMTP id 1CECC20997 for ; Wed, 3 Sep 2014 15:25:45 -0400 (EDT) Received: from frontend1 ([10.202.2.160]) by compute1.internal (MEProxy); Wed, 03 Sep 2014 15:25:45 -0400 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=aklaver.com; h= message-id:date:from:mime-version:to:cc:subject:references :in-reply-to:content-type:content-transfer-encoding; s=mesmtp; bh=+ZMdC6W+0Ic3LfxKQnrRaZD8Hhk=; b=DVbLJbgHlgIYW/V4KTUcG5+T1fkY 0iy+4aYsyw4DEMWSgrCXzN3H3pTjMbyWGqpKEMkfZ7GVYXK14t9rJFrfNKtUITlr skXR17WA0HVtaIbSYUjmBqNvYz9AkG/3eSuQMnFkzTbSHCyzwVm6jlYyr1r/T8W0 uakoJs1MxK+9z/Q= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:date:from:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; s=smtpout; bh=+ZMdC6W+0Ic3LfxKQnrRaZ D8Hhk=; b=TjSP3miIaaVdfgt2disAcKacWoTPHABABAEvvWyFaM1xAcCyPD1bIi p6XRBiv1R++5tqmQI+6HwvPmnXON1q0f6iCqmVk3KrrgQ1lg3L1nSpn5JWJ8afmC ETadOJOC/1g9SCphqH/VUcKqTx1Dj4NLdL11uV/WtdjMXFCOITj/A= X-Sasl-enc: B7a+ZQKh3eckckHVO8GAhgdJXSzntbCXoIAOA4xi3vOe 1409772344 Received: from [192.168.1.5] (unknown [174.21.177.1]) by mail.messagingengine.com (Postfix) with ESMTPA id 5B7D3C0091F; Wed, 3 Sep 2014 15:25:44 -0400 (EDT) Message-ID: <54076B37.7000603@aklaver.com> Date: Wed, 03 Sep 2014 12:25:43 -0700 From: Adrian Klaver User-Agent: Mozilla/5.0 (X11; Linux i686; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: Alanoly Andrews , 'Craig James' CC: "pgsql-admin@postgresql.org" , "pgsql-general@postgresql.org" Subject: Re: Re: [ADMIN] Cannot retrieve images inserted through VB and odbc, after a table reorganization. References: <6909b219ecae4d41b431efdaf6c953a3@Exch2.invera.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Pg-Spam-Score: -2.7 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-general Precedence: bulk Sender: pgsql-general-owner@postgresql.org On 09/03/2014 09:26 AM, Alanoly Andrews wrote: > *Hi Craig,* > > ** > > *I’m reloading into the very same database. * > > *If I insert a new row into the table (through VB/ODBC), I’m able to > retrieve it (again from VB). But if after inserting the new row, I do a > reorg of the table (eg. with a “cluster table”), I’m no longer able to > retrieve that same row. In short, as long as the newly inserted rows are > not “re-written” in some way, they can be retrieved through VB/ODBC. * This: Note the OID for the table stays the same but the relfilenode changes. This also happens with the other situations you describe(unless you use --oids with pg_dump). should be: Note the OID for the table stays the same but the relfilenode changes. This also happens with the other situations you describe(if you use --oids with pg_dump). > > ** > > *Alanoly.* > -- Adrian Klaver adrian.klaver@aklaver.com -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general