Thanks for the tip.
I want to try new pg_dump to connect to old server, but i can't - old
postgres doesn't listening to network socket. Why postgres 6.5.3 not
binding to network socket? It started with this line:
su pgsql -c '/usr/local/pgsql/bin/postmaster -d 5 -p 5432 -S -o "-e -F"
-D /usr/local/pgsql/data' >/var/log/postgres.log 2>&1 &
There is no errors in logfile about network socket, and postgres not
listening to network:
# sockstat | grep 5432
#
While postgres is up and running
# ps ax | grep postgres
47034 ?? Is 0:00.03 /usr/local/pgsql/bin/postmaster -d 5 -p 5432
-S -o -e -F -D /usr/local/pgsql/data (postgres)
And here's the logfile:
FindExec: found "/usr/local/pgsql/bin/postgres" using argv[0]
binding ShmemCreate(key=52e2c1, size=1001472)
Kenneth Marshall wrote:
> When upgrading, you use the pg_dump from the new version to
> dump the old database. Then it can take care of incidental
> changes during the process. I think that the mailing list
> archives have articles on upgrading from v6.5. I do not think
> that you can go straight from v6.5 to v8.3. You will almost
> certainly need to use v7.2-7.4 as a intermediate step, maybe
> v8.0 will work, check the list archives. Good luck.
>
> Cheers,
> Ken
>
> On Thu, Aug 14, 2008 at 10:34:11AM -0400, David Blewett wrote:
>> On Thu, Aug 14, 2008 at 9:58 AM, alexander lunyov <lan@zato.ru> wrote:
>>> Hello everybody.
>>>
>>> We have a dusty old server, FreeBSD 3.3-RELEASE, PostgreSQL 6.5.3.
>>> I need to migrate four DBs from old server to new server (FreeBSD 6.2,
>>> PostgreSQL 8.3.1).
>> Just an FYI: I advised Alexander to post here, because I thought some
>> of the devs might have older pg installs/dump tools and might be able
>> to give some advice.
>>
>> David Blewett
>>
>> --
>> Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
>> To make changes to your subscription:
>> http://www.postgresql.org/mailpref/pgsql-hackers
>>
>
--
alexander lunyov
