Re: [GENERAL] How to transfer from place to plase without backup/restore

[anvesh]

It can done through cloud based services like using drop box or google drive. 
Happy Rose Day

  
They have worked like a charm for me.. Happy Chocolate Day
   I think there are various number of other 3rd
party applications that have been  Happy Valentines Day Quotes
   developed in the later
months  Hug Day 2016

  



--
View this message in context: 
http://postgresql.nabble.com/How-to-transfer-from-place-to-plase-without-backup-restore-tp1890462p5884194.html
Sent from the PostgreSQL - general mailing list archive at Nabble.com.


-- 
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general

Re: [GENERAL] How to transfer from place to plase without backup/restore

[Hristo Filipov]

Man ... well :-), thanks for the answer. At least I'll stop running against
the wall.

-Original Message-
From: Alvaro Herrera [mailto:[EMAIL PROTECTED] 
Sent: 06 ??? 2007 00:11
To: Hristo Filipov
Cc: 'Shane Ambler'; pgsql-general@postgresql.org
Subject: Re: [GENERAL] How to transfer from place to plase without
backup/restore

Hristo Filipov wrote:

> Is there a way to tell PostgreSQL not install itself with OS or/and CPU
> compatibility(for the prize of loosing performance), but that way the one
> can move files free from on Computer to another?

No, there isn't.

-- 
Alvaro Herrera
http://www.PlanetPostgreSQL.org/
"Uno combate cuando es necesario... ¡no cuando está de humor!
El humor es para el ganado, o para hacer el amor, o para tocar el
baliset.  No para combatir."  (Gurney Halleck)


---(end of broadcast)---
TIP 4: Have you searched our list archives?

   http://archives.postgresql.org/

Re: [GENERAL] How to transfer from place to plase without backup/restore

[Alvaro Herrera]

Hristo Filipov wrote:

> Is there a way to tell PostgreSQL not install itself with OS or/and CPU
> compatibility(for the prize of loosing performance), but that way the one
> can move files free from on Computer to another?

No, there isn't.

-- 
Alvaro Herrera   http://www.PlanetPostgreSQL.org/
"Uno combate cuando es necesario... ¡no cuando está de humor!
El humor es para el ganado, o para hacer el amor, o para tocar el
baliset.  No para combatir."  (Gurney Halleck)

---(end of broadcast)---
TIP 6: explain analyze is your friend

Re: [GENERAL] How to transfer from place to plase without backup/restore

[Hristo Filipov]

Hi Shane,
Thanks for the answer.
Actually I want to distribute specific database to a lot of different
clients(different OS/Linux;Windows/, different CPU/AMD;Intel/), and I was
thinking about only copying the files instead of dump/restore(which is must
slower operation). From your answer I guess it is impossible for now :-(.
Is there a way to tell PostgreSQL not install itself with OS or/and CPU
compatibility(for the prize of loosing performance), but that way the one
can move files free from on Computer to another?

Hristo Filipov

-Original Message-
From: Shane Ambler [mailto:[EMAIL PROTECTED] 
Sent: 23  2007 11:58
To: Hristo Filipov
Cc: pgsql-general@postgresql.org
Subject: Re: [GENERAL] How to transfer from place to plase without
backup/restore

Hristo Filipov wrote:
> Is it possible to transfer database from one place to another without
making
> backup from the source and restore at the target? 
> 
> I mean I want to copy the files as they are at the source to the target?
> What else I must do, so I can attach them to the target PostgreSQL
database?

That is basically what you are doing when you transfer (unless you are 
moving the drive to a new machine) - how you do the transfer will depend 
on your needs and what hardware and software is at the source and 
destination.

If you are looking for a backup server to be ready to use as soon as 
your production server fails then you can look at PITR or 
synchronization such as slony-1

If you want to copy your database to a development machine occasionally, 
then if they have the same hardware and postgres version then you should 
be able to copy the data files across while the production server is 
stopped without problems. Some differences between CPU and postgres 
version can stop this from working.

You could also do the dump/restore directly from one machine to another 
if they are on the same network without having the dump file to transfer 
across and import which will give similar results.

eg. instead of -
pg_dumpall > mybackupfile
psql -h my.other.machine.address < mybackupfile

you can -

pg_dumpall | psql -h my.other.machine.address

If you have different cpu's (one Intel and one AMD64) or different 
postgres versions then you will have to do the dump/restore even if it 
is sent straight from one to another.

For more help specify what hardware, system and postgres version you 
have on each machine and what you wish to achieve in transferring.



-- 

Shane Ambler
[EMAIL PROTECTED]

Get Sheeky @ http://Sheeky.Biz


---(end of broadcast)---
TIP 9: In versions below 8.0, the planner will ignore your desire to
   choose an index scan if your joining column's datatypes do not
   match

Re: [GENERAL] How to transfer from place to plase without backup/restore

[Shane Ambler]

Hristo Filipov wrote:

Is it possible to transfer database from one place to another without making
backup from the source and restore at the target? 


I mean I want to copy the files as they are at the source to the target?
What else I must do, so I can attach them to the target PostgreSQL database?


That is basically what you are doing when you transfer (unless you are 
moving the drive to a new machine) - how you do the transfer will depend 
on your needs and what hardware and software is at the source and 
destination.


If you are looking for a backup server to be ready to use as soon as 
your production server fails then you can look at PITR or 
synchronization such as slony-1


If you want to copy your database to a development machine occasionally, 
then if they have the same hardware and postgres version then you should 
be able to copy the data files across while the production server is 
stopped without problems. Some differences between CPU and postgres 
version can stop this from working.


You could also do the dump/restore directly from one machine to another 
if they are on the same network without having the dump file to transfer 
across and import which will give similar results.


eg. instead of -
pg_dumpall > mybackupfile
psql -h my.other.machine.address < mybackupfile

you can -

pg_dumpall | psql -h my.other.machine.address

If you have different cpu's (one Intel and one AMD64) or different 
postgres versions then you will have to do the dump/restore even if it 
is sent straight from one to another.


For more help specify what hardware, system and postgres version you 
have on each machine and what you wish to achieve in transferring.




--

Shane Ambler
[EMAIL PROTECTED]

Get Sheeky @ http://Sheeky.Biz

---(end of broadcast)---
TIP 9: In versions below 8.0, the planner will ignore your desire to
  choose an index scan if your joining column's datatypes do not
  match