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

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Mike Wilson <mfwilson(at)gmail(dot)com>
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 01:52:41
Message-ID: 20120713015241.GA15443@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-hackers

On Thu, Jul 12, 2012 at 05:21:31PM -0700, Mike Wilson wrote:
> 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

Uh, actually, a hard link has two directory entries pointing to the same
file, so you can delete the old datadir and the new datadir should not
be affected.

--
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 Craig Ringer 2012-07-13 10:55:46 Re: BUG #6697: postgres.exe crashed
Previous Message Mike Wilson 2012-07-13 00:21:31 Re: BUG #6733: All Tables Empty After pg_upgrade (PG 9.2.0 beta 2)

Browse pgsql-hackers by date

  From Date Subject
Next Message Etsuro Fujita 2012-07-13 02:02:17 Re: WIP Patch: Selective binary conversion of CSV file foreign tables
Previous Message Jose Ildefonso Camargo Tolosa 2012-07-13 01:36:26 Re: Synchronous Standalone Master Redoux