On 07/20/2014 11:28 AM, Steve Atkins wrote:
On Jul 20, 2014, at 11:09 AM, maillis...@gmail.com wrote:
I send a nightly dump of my production database to a development server. A
script drops the existing development database and replaces it with the current
production copy.
Each dev uses her
On Jul 20, 2014, at 11:09 AM, maillis...@gmail.com wrote:
> I send a nightly dump of my production database to a development server. A
> script drops the existing development database and replaces it with the
> current production copy.
>
> Each dev uses her own copy of the database. Is there
I send a nightly dump of my production database to a development server. A
script drops the existing development database and replaces it with the
current production copy.
Each dev uses her own copy of the database. Is there a way to copy the
current development database to a differently named db
On Donnerstag, Dez 15, 2005, at 12:11 Europe/Berlin, Tino Wildenhain
wrote:
Marc Brünink schrieb:
Hi list,
...
Now I'l try a custom dump. Perhaps this will suffice. But I guess
it's impossible for a dump to be as fast as a cp. So if a cp would
be possible I would favour it. Oh, and did I
Marc Brünink schrieb:
Hi list,
...
Now I'l try a custom dump. Perhaps this will suffice. But I guess it's
impossible for a dump to be as fast as a cp. So if a cp would be
possible I would favour it. Oh, and did I tell: Everything have to be
done tommorow. *sigh*
Actually its faster.
This link explains lot of useful techniques for backup and restore
http://www.postgresql.org/docs/8.1/static/backup.html
On 12/15/05, Marc Brünink <[EMAIL PROTECTED]> wrote:
> Hi list,
>
> I know this was asked a lot of times on this mailing list. But actually
> no reply satisfied me :-)
> Howeve
Hi list,
I know this was asked a lot of times on this mailing list. But actually
no reply satisfied me :-)
However: I've a running postgres database. It's about 6 GB big. Now I
want to copy this database to another host. Clearly pg_dumpall comes to
the mind. But there're 2 problems:
1. The n
