If I leave the trust authentication server, the program runs correctly. change
is that the exec () does not add the env variable
2011/9/8 Miguel Angel Hernandez Moreno
> sorry
>
>
> comando=: "C:\Program Files\pgAdmin III\1.12\pg_restore.exe" -h
> 192.170.1.89 -d postgres -U postgres -v -1 "C:\
sorry
comando=: "C:\Program Files\pgAdmin III\1.12\pg_restore.exe" -h 192.170.1.89
-d postgres -U postgres -v -1 "C:\Users\Miguel\Documents\
NetBeansProjects\file.backup"
2011/9/8 Miguel Angel Hernandez Moreno
> Sorry
>
> This is the error that sends me
>
> pg_restore: connecting to databas
Sorry
This is the error that sends me
pg_restore: connecting to database for restore
pg_restore: [archiver (db)] connection to database "postgres" failed: could
not create socket: Unknown socket error (0x277A/10106)
pg_restore: *** aborted because of error
And this is the value of my variabl
On Thu, Sep 8, 2011 at 10:45 AM, Miguel Angel Hernandez Moreno
wrote:
> Hello
>
> I have a program in java to make a backup running pg_restore, If you use
> linux give a successful outcome.
> but if you use windows I mark an error generating the socket. I think that
> it could be the environment v
Hello
I have a program in java to make a backup running pg_restore, If you use
linux give a successful outcome.
but if you use windows I mark an error generating the socket. I think that
it could be the environment variables in Windows.
My java code is as follows.
String comando="";
String env[]
You are right again.
I don't want to make permanet changes for this one-time problem.
Yes I find a way to
Use pg_restore to make a text dump script, and then edit that, and then
load it into your newer server.
- pg_restore can output to file not only database. I will edit this file.
Thanks.
Kaloyan
Kaloyan Iliev Iliev <[EMAIL PROTECTED]> writes:
> But as I say the file with copy commands contains
> [EMAIL PROTECTED]@[EMAIL PROTECTED] [EMAIL PROTECTED]@[EMAIL
> PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL
> PROTECTED]@[EMAIL PROTECTED]@COPY "tracking_base" FROM
>
But as I say the file with copy commands contains
[EMAIL PROTECTED]@[EMAIL PROTECTED] [EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@COPY "tracking_base" FROM
stdin;
[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]
Kaloyan Iliev Iliev <[EMAIL PROTECTED]> writes:
> You are right. I coleage of mine has added the delete column after the
> schema was created and it ptobably was on the bottom of the table and
> dumped there. But now when I restore the schema this column is on the
> top and the copy command woul
Kaloyan Iliev Iliev wrote:
Hi ,
I have the following problem.
DBVersion: PostgreSQL 7.2.3 on i386-pc-bsdi4.0.1, compiled by GCC 2.7.2.1
I have a dump of a database on two parts.
Here are the dump commands:
pg_dump -s -S postgres "db_name" |gzip > "db_name.shema.sql"
pg_dump -S postgres -a -Fc "db
Thanks Tom,
You are right. I coleage of mine has added the delete column after the
schema was created and it ptobably was on the bottom of the table and
dumped there. But now when I restore the schema this column is on the
top and the copy command wouldn't work. So I must change the schema file
Kaloyan Iliev Iliev <[EMAIL PROTECTED]> writes:
> [ details omitted ]
The easiest way around this is to use a recent (7.4 or 8.0) pg_dump to
dump from the 7.2 database. That will produce a dump using copy-with-
column-list commands which will be proof against the schema
rearrangement that you see
Hi ,
I have the following problem.
DBVersion: PostgreSQL 7.2.3 on i386-pc-bsdi4.0.1, compiled by GCC 2.7.2.1
I have a dump of a database on two parts.
Here are the dump commands:
pg_dump -s -S postgres "db_name" |gzip > "db_name.shema.sql"
pg_dump -S postgres -a -Fc "db_name" > "db_name.data.dump
[EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] Behalf Of andy morrow
> Sent: 02 July 2003 15:17
> To: [EMAIL PROTECTED]
> Subject: [GENERAL] problems with pg_restore to 7.3.3 db
>
>
> hi,
>
> fairly new to postgres admin stuff..
>
> i have a production machine that i
hi,
fairly new to postgres admin stuff..
i have a production machine that is running postgresql 7.1.3
also, there's a test machine which already had 7.0.3, and which i newly
installed 7.3.3
so, i dumped all the databases from the production db and reloaded on the
test,
there was a few proble
15 matches
Mail list logo
