From: | Sean Davis <sdavis2(at)mail(dot)nih(dot)gov> |
---|---|
To: | fasupport(at)allcoast(dot)net |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Distributing PostGres database to various customers |
Date: | 2007-06-11 13:54:13 |
Message-ID: | 466D5405.5020409@mail.nih.gov |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Mike Gould wrote:
> All,
>
> I am new to PostGres 8 (using 8.2.4 windows version). We have for
> several years been using iAnywhere's SQL Anywhere product with our
> commercial transportation software. With ASA there are 2 files that
> must be distributed for the database, a filename.db and a filename.log.
> When we do a new installation we normally try and preload the database
> with data used for lookups, some registration data and if a customer is
> moving from another software where we've been contracted to convert
> their old data to our system we preload that. Once that is done we can
> distribute the database as part of the setup process.
>
> How can we do this with PostGres? Other than backup and restore or
> creating SQL scripts I haven't been able to find another method. Some
> of these tables may have over a million rows in them initially if we
> convert old data.
I would give backup/restore a try. A million rows isn't very big in
postgres terms. On relatively low-end hardware, I am routinely able to
backup about 300Gb in about 35 databases in under 3 hours.
Sean
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2007-06-11 13:55:13 | Re: track ddl changes on single database |
Previous Message | Martijn van Oosterhout | 2007-06-11 13:40:58 | Re: transaction problem using cursors |