Not even close. PostgreSQL uses one or more files per
table/index/sequence/etc. Each database has its own directory. I think
with tablespaces you can even spread a database over multiple
directories.
Secondly, every connection gets its very own postmaster, they can can
each access any file they wish.
Hope this helps,
On Mon, Sep 06, 2004 at 02:47:56AM +0000, Randy Yates wrote:
> I'm a complete newbie to postgres so please look the
> other way if these questions are really stupid.
>
> Is it legitimate to have one database per data file? For
> organizational and backup purposes, I'd like to keep the
> database files for each of several projects separate.
> This means, e.g., that postmaster must have multiple
> instances going simultaneously?
>
> I'm thinking the answer is NO because, for one, the TCPIP
> connection seems to be to ONE instance of postmaster which
> then sorts out which database objects are in its container.
>
> Am I close?
--
Martijn van Oosterhout <kleptog@svana.org> http://svana.org/kleptog/
> Patent. n. Genius is 5% inspiration and 95% perspiration. A patent is a
> tool for doing 5% of the work and then sitting around waiting for someone
> else to do the other 95% so you can sue them.