transferring to new computer - stumped and frustrated

[Kestral123]

So, here's the setup of the problem. My old laptop has a power problem, so I can no longer use it (can't charge the battery and won't run on direct power). I can, however, attach the hard drive to my new laptop as an external hard drive.

So, I'm trying to migrate my PT database to my new computer (Vista). On my old computer, I was running PT3 on postgreSQL 8.2 in XP. This was a continuation of a previous PT2 database.

The first thing I tried was just copying the 8.3 folder to the new computer. I didn't expect that to work, and it didn't. So, using some of my precious battery power, I backed-up using pg-admin. For some reason I appeared to have two (or maybe three) databases listed under the 8.3 server in PGadmin. One was called "My Poker DB", one was called "PT3 DB" and the other was just postgreSQL. I backed up the first two and have subsequently tried restoring both of them. They seem to function but are incomplete, with only 11 tourneys showing, and a few hundred hands of ring games.

So, I'm lost. Any suggestions? I'm at the point now where I can't run the old computer unless/until I can find a way to charge the battery, so I'm limited to either doing something with the backup files, or (as noted) I can still fully access the hard drive from my old laptop via USB connection.

HELP!

[WhiteRider]

Please clarify which version of postgres you had on the old computer? You say you had 8.2, but that you copied the 8.3 folder?

If you have the same version of postgres on both, they you should be able to reconnect to your 'data' folder - have a look at the Database / Postgres FAQ.

I think the database you should be restoring is likely to be "PT3 DB".
How many hands were there in the old database?

I'll ask someone who knows more about postgres to take a look at this thread.

[Kestral123]

I misspoke - I am (was) running 8.2 on my old computer.

[WhiteRider]

I'll get someone who knows more about postgres to take a look at this thread, but if the databases have restored I fear that you may have got what you're going to get out of them.

Just confirm that you have no filters set that might be preventing hands being shown - click Clear.

[kraada]

If you had 8.2 on the old computer you have to install 8.2 on the new computer in order to be able to read from the same data directory. The data directories are stored differently between PostgreSQL 8.2 and 8.3.

Install 8.2 on your new computer, edit the postgresql.conf (Start --> Programs --> PostgreSQL --> Edit PostgreSQL.conf) and set the data directory to point to your backup from the old computer.

Then backup per the FAQ once you have it up and running and you'll be able to restore it in 8.3, but you can't just use the data directory from one version in another.

[Kestral123]

Well, I tried doing a complete uninstall. As complete as I can do anyway. I uninstalled PT3 and postgreSQL and then deleted every trace of the two. However, when I reinstalled postgreSQL 8.2, and tried to access the database through pgadmin, I got a "Server can't listen" error. Now what?

[Kestral123]

Disregard previous post. I managed to get the installation. I changed the data directory configuration to e:\PT3 backup.backup. I stopped and restarted the service, but I keep getting a "server doesn't listen" error. What now?

[WhiteRider]

Did you do the 'net user postgres /delete' part of the uninstall?
(Total uninstall/reinstall of pt3)

I'll bump this for Kraada again.

[kraada]

Could you please copy and paste the contents of your pg_hba.conf file into this thread? If that's misconfigured it can give this sort of error. (Start --> Programs --> PostgreSQL --> Edit pg_hba.conf)

[Kestral123]

Yes, I did that step in the uninstall process. Here are the contents of that file:

# PostgreSQL Client Authentication Configuration File
# ===================================================
#
# Refer to the "Client Authentication" section in the
# PostgreSQL documentation for a complete description
# of this file. A short synopsis follows.
#
# This file controls: which hosts are allowed to connect, how clients
# are authenticated, which PostgreSQL user names they can use, which
# databases they can access. Records take one of these forms:
#
# local DATABASE USER METHOD [OPTION]
# host DATABASE USER CIDR-ADDRESS METHOD [OPTION]
# hostssl DATABASE USER CIDR-ADDRESS METHOD [OPTION]
# hostnossl DATABASE USER CIDR-ADDRESS METHOD [OPTION]
#
# (The uppercase items must be replaced by actual values.)
#
# The first field is the connection type: "local" is a Unix-domain socket,
# "host" is either a plain or SSL-encrypted TCP/IP socket, "hostssl" is an
# SSL-encrypted TCP/IP socket, and "hostnossl" is a plain TCP/IP socket.
#
# DATABASE can be "all", "sameuser", "samerole", a database name, or
# a comma-separated list thereof.
#
# USER can be "all", a user name, a group name prefixed with "+", or
# a comma-separated list thereof. In both the DATABASE and USER fields
# you can also write a file name prefixed with "@" to include names from
# a separate file.
#
# CIDR-ADDRESS specifies the set of hosts the record matches.
# It is made up of an IP address and a CIDR mask that is an integer
# (between 0 and 32 (IPv4) or 128 (IPv6) inclusive) that specifies
# the number of significant bits in the mask. Alternatively, you can write
# an IP address and netmask in separate columns to specify the set of hosts.
#
# METHOD can be "trust", "reject", "md5", "crypt", "password",
# "krb5", "ident", "pam" or "ldap". Note that "password" sends passwords
# in clear text; "md5" is preferred since it sends encrypted passwords.
#
# OPTION is the ident map or the name of the PAM service, depending on METHOD.
#
# Database and user names containing spaces, commas, quotes and other special
# characters must be quoted. Quoting one of the keywords "all", "sameuser" or
# "samerole" makes the name lose its special character, and just match a
# database or username with that name.
#
# This file is read on server startup and when the postmaster receives
# a SIGHUP signal. If you edit the file on a running system, you have
# to SIGHUP the postmaster for the changes to take effect. You can use
# "pg_ctl reload" to do that.

# Put your actual configuration here
# ----------------------------------
#
# If you want to allow non-local connections, you need to add more
# "host" records. In that case you will also need to make PostgreSQL listen
# on a non-local interface via the listen_addresses configuration parameter,
# or via the -i or -h command line switches.
#



# TYPE DATABASE USER CIDR-ADDRESS METHOD

# IPv4 local connections:
host all all 127.0.0.1/32 md5
# IPv6 local connections:
host all all ::1/128 md5