Tom, after patching pg_upgrade now runs successfully. I noticed that this
patch had been applied since yesterday to the REL9_2_STABLE so I also tested
with a git pull without the patch that appears to work also. I think issue has
been resolved for me, thanks so much! You guys rock!
Mike
On Sun, Jul 15, 2012 at 02:15:35PM -0700, Mike Wilson wrote:
I've had some time to examine this closer over the weekend. It appears that
pg_upgrade for 9.2b2 segfaults which more than likely has something to do with
the resulting converted database appearing to have no rows. Earlier in this
On Tue, Jul 17, 2012 at 04:01:08PM -0700, Mike Wilson wrote:
Please find below the full pg_upgrade output. Let me know if there are any
other questions that I may have missed. Note, the attached pg_upgrade stdout
log is for the schema only pg_dumpall upgrade attempt from PG842 - PG920b2.
On Tue, Jul 17, 2012 at 05:41:05PM -0700, Mike Wilson wrote:
Given the stack trace previously supplied and that the pg_upgrade from 9.1.4
does actually complete successfully can you recommend how I might continue to
diagnose the issue myself? Since the 9.1.4 version of pg_upgrade did work
Bruce Momjian br...@momjian.us writes:
I am using git head for testing. Tom sees a few things odd in
load_directory() that might be causing some problems on Solaris, and
this is new code for 9.2 for Solaris, so that might explain it. I think
we need Tom to finish and then if you can grab our
core stack:
root@db4 / $ pstack ~postgres/core
core '/opt/postgres/core' of 19868: pg_upgrade --verbose --link
--old-datadir=/opt/postgres/db/root/old --
fd7ffeda1148 memcpy () + 6b8
0040b8b6 transfer_single_new_db () + fa
0040b6ea transfer_all_new_dbs () + 116
Just for my interest I also created a new PG 842 db (initdb) and put some
sample data it it and successfully did a pg_upgrade from 842 - 920b2.
Whatever the issue is it seems to be related to my actual database as a sample
db conversion works. Again, 842-914 conversion works for my db though
Mike Wilson mfwil...@gmail.com writes:
Just for my interest I also created a new PG 842 db (initdb) and put
some sample data it it and successfully did a pg_upgrade from 842 -
920b2. Whatever the issue is it seems to be related to my actual
database as a sample db conversion works.
Yeah, I
I've had some time to examine this closer over the weekend. It appears that
pg_upgrade for 9.2b2 segfaults which more than likely has something to do with
the resulting converted database appearing to have no rows. Earlier in this
thread I reported that I was able to get the upgrade to work
Mike Wilson mfwil...@gmail.com writes:
I've had some time to examine this closer over the weekend. It
appears that pg_upgrade for 9.2b2 segfaults which more than likely has
something to do with the resulting converted database appearing to
have no rows.
Yeah, more than likely :-(. Could we
The following bug has been logged on the website:
Bug reference: 6733
Logged by: Mike Wilson
Email address: mfwil...@gmail.com
PostgreSQL version: 9.1.4
Operating system: Solaris 10
Description:
Filing this under PG914 since there isn't an option for PG9.2beta2.
mfwil...@gmail.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
On Thu, Jul 12, 2012 at 10:16:18PM +, mfwil...@gmail.com wrote:
The following bug has been logged on the website:
Bug reference: 6733
Logged by: Mike Wilson
Email address: mfwil...@gmail.com
PostgreSQL version: 9.1.4
Operating system: Solaris 10
Description:
On Thu, Jul 12, 2012 at 06:44:06PM -0400, Tom Lane wrote:
mfwil...@gmail.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
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
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,
16 matches
Mail list logo
