A.M. wrote:
You know that you don't have to compile postgresql as "Universal",
right? If you have separate PPC and Intel versions (not lipo'd
together), then, presumably, you should be able to figure out which one
needs to run. The PPC postgresql would then run on the Macintel under
Rosetta a
On May 12, 2008, at 4:02 PM, Chris Saldanha wrote:
Hi,
We'd like to ship PostgreSQL as part of a product that runs on both
PPC and
Intel Macs, but the database files are tied to the build settings and
endianness of the computer that the database was initialized on.
Is there any way to caus
> Maybe it's an opportunity to introduce the users to backups.
Yes, we do backups for the user, but the problem with Apple's migration is
that it happens not on a schedule that meshes with the backup schedule. Our
applications have fairly frequently changing data.
> Honestly, though, PostgreSQL
Merlin Moncure wrote:
Surely it's easier just to have your application dump on schedule and
add some front end GUI import feature to your app? It looks like you
are maybe trying to solve the wrong problem...namely that it is too
difficult for your users to do backup/restore themselves.
Maybe
On Mon, May 12, 2008 at 4:02 PM, Chris Saldanha
<[EMAIL PROTECTED]> wrote:
> We'd like to ship PostgreSQL as part of a product that runs on both PPC and
> Intel Macs, but the database files are tied to the build settings and
> endianness of the computer that the database was initialized on.
>
>
Hi,
We'd like to ship PostgreSQL as part of a product that runs on both PPC and
Intel Macs, but the database files are tied to the build settings and
endianness of the computer that the database was initialized on.
Is there any way to cause the server to modify the database files in-place
for end
