From: | Gail Zacharias <gz(at)clozure(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | database files |
Date: | 2003-10-22 19:41:35 |
Message-ID: | 5.2.1.1.0.20031022152614.050db770@127.0.0.1 |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
I am investigating the possibility of using pgsql as the database in an application. I have some unusual requirements that I'd like to ask you all about. I apologize in advance if my terminology is a little "off", I'm not familiar with pgsql (yet).
I need to be able to move the database files, as normal user-visible files, between machines. I.e. given a database on machine A, I want to be able to copy either a single file (ideally) or a single directory (less ideal but still ok) to, say, a zip drive, bring it over to another machine (with pgsql also installed), start up my application and have it access the copied database through pgsql.
Is this sort of thing possible? Is a database stored in a single file or multiple files? Can the location of the file(s) be controlled? Are the files accessible and consistent while pgsql is running? I assume not all the time, but is there a reliable way to make them accessible (i.e. copyable) and consistent short of shutting down pgsql?
Is the file format of the pgsql database files compatible between OS's? E.g. could I take some database files from Linux and use them on Windows?
Thanks in advance for any advice,
Gail Zacharias
From | Date | Subject | |
---|---|---|---|
Next Message | Oksana Yasynska | 2003-10-22 19:59:05 | Re: plpgsql: return multiple result sets or temp table |
Previous Message | Gail Zacharias | 2003-10-22 19:40:41 | Adding fields on the fly |