Tom Lane wrote:
Of course, since you got the data migrated you might not care anymore.
That's what i've done:
1. pg_dump database from 6.5.3
2. iconv from windows-1251 charset to utf-8.
3. cutted all AGGREGATEs
4. succesefully imported all data to 8.3.1 without errors.
Seems to me everything n
alexander lunyov <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>>> I wonder if you need these self defined aggregates at all, most or all
>>> of them are in 8.3 already.
>>
>> They aren't "self defined" in 6.5 either.
> So i can't just delete those AGGREGATEs?
>> I think what is happening
>>
Tom Lane wrote:
A further suggestion is that you use -d or even -D option on the dump.
I think there have been some corner-case changes in COPY data format
since 6.5 days; which might or might not bite you, but why take the
chance ...
%/usr/local/pgsql/bin/pg_dump -D itt_user > itt_user.dump
B
Tom Lane wrote:
alexander lunyov <[EMAIL PROTECTED]> writes:
I want to try new pg_dump to connect to old server, but i can't - old
postgres doesn't listening to network socket.
It won't work anyway: modern versions of pg_dump are only designed to
work with servers back to 7.0. I see from the
Tom Lane wrote:
I wonder if you need these self defined aggregates at all, most or all
of them are in 8.3 already.
They aren't "self defined" in 6.5 either.
So i can't just delete those AGGREGATEs?
I think what is happening
is that he's trying to force a 7.x pg_dump to dump from the 6.5 s
Andreas Pflug <[EMAIL PROTECTED]> writes:
> I wonder if you need these self defined aggregates at all, most or all
> of them are in 8.3 already.
They aren't "self defined" in 6.5 either. I think what is happening
is that he's trying to force a 7.x pg_dump to dump from the 6.5 server
(with -i no
alexander lunyov <[EMAIL PROTECTED]> writes:
> I want to try new pg_dump to connect to old server, but i can't - old
> postgres doesn't listening to network socket.
It won't work anyway: modern versions of pg_dump are only designed to
work with servers back to 7.0. I see from the rest of the thre
Guillaume Smet wrote:
On Fri, Aug 15, 2008 at 11:42 AM, alexander lunyov <[EMAIL PROTECTED]> wrote:
i didn't find anything like postgresql.conf on old server. Right now i'm
tried to start 6.5.3 on windows (downloaded binary from ftp archive on
postgresql.org, installed last cygwin) with the data
alexander lunyov wrote:
Andreas Pflug wrote:
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:
Maybe you should just dump schema and data separately w
On Fri, Aug 15, 2008 at 11:42 AM, alexander lunyov <[EMAIL PROTECTED]> wrote:
> i didn't find anything like postgresql.conf on old server. Right now i'm
> tried to start 6.5.3 on windows (downloaded binary from ftp archive on
> postgresql.org, installed last cygwin) with the data dir from old serve
Andreas Pflug wrote:
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:
Maybe you should just dump schema and data separately with your old
pg_dump too
alexander lunyov wrote:
Guillaume Smet wrote:
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:
Maybe you should just dump schema and data separately
Guillaume Smet wrote:
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:
Do you have something like tcpip_socket in your postgresql.conf (I
don't know if
On Fri, Aug 15, 2008 at 9:54 AM, alexander lunyov <[EMAIL PROTECTED]> wrote:
> 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:
I think that you use to much new pg_dump. I'm not sure but my expectation is
that latest pg_dump version does not support too old PG. The problem there could
be network protocol. Currently only version 3 and 2 is supported. I recommend
you to jump to 7.x (7.2) first and use 7.2 pg_dump and after
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/loc
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
On Thu, Aug 14, 2008 at 9:58 AM, alexander lunyov <[EMAIL PROTECTED]> 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 p
18 matches
Mail list logo
