Re: BUG #6733: All Tables Empty After pg_upgrade (PG 9.2.0 beta 2)

From: Mike Wilson <mfwilson(at)gmail(dot)com>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #6733: All Tables Empty After pg_upgrade (PG 9.2.0 beta 2)
Date: 2012-07-13 00:21:31
Message-ID: 517A874F-B310-4340-803D-EC8625C8B497@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-hackers

This can be closed. I figured out what I was doing wrong, which was after the conversion I was cleaning up the old datadir by deleting it, which destroyed the hard links to the data since I am using pg_upgrade --link

Mike Wilson

On Jul 12, 2012, at 3:49 PM, Bruce Momjian wrote:

> On Thu, Jul 12, 2012 at 06:44:06PM -0400, Tom Lane wrote:
>> mfwilson(at)gmail(dot)com writes:
>>> This runs without errors and I am able to start the new upgraded PG92beta2
>>> cluster. The schemas appear to be correct as well as the table definitions
>>> and other schema objects. The tables themselves though are all empty.
>>
>> Hmm, maybe it's confused about XID past/future? Could we see the output
>> of pg_controldata for both old and new clusters?
>
> Uh, I thought we only changfed the xlog stuff in 9.3, not 9.2, so I am
> confused what would have changed in that area.
>
> --
> Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
> EnterpriseDB http://enterprisedb.com
>
> + It's impossible for everything to be true. +

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Bruce Momjian 2012-07-13 01:52:41 Re: BUG #6733: All Tables Empty After pg_upgrade (PG 9.2.0 beta 2)
Previous Message Christian Ullrich 2012-07-13 00:04:50 Re: BUG #6732: Build issue when using gettext on FreeBSD 9

Browse pgsql-hackers by date

  From Date Subject
Next Message Jose Ildefonso Camargo Tolosa 2012-07-13 00:27:01 Re: Synchronous Standalone Master Redoux
Previous Message Harold A. Giménez 2012-07-12 23:21:13 Re: DELETE vs TRUNCATE explanation