On Jun 25, 2009, at 9:26 PM, Jack W wrote:
> I can not shut down
> just one database because all the the databases will be shut
down, right?
True, but why are you shutting databases down?
Maybe for maintainence purpose or schema change. For example as you
mentioned above, if using several
2009/6/25 Jack W
>
> Maybe for maintainence purpose or schema change. For example as you
> mentioned above, if using several tablespaces located on different hard
> drives. If one hard drive is damaged, the database on that hard drive will
> not be available. How about other databases managed by
On Thu, Jun 25, 2009 at 12:10 PM, Bill Moran wrote:
> In response to Jack W :
>
> > On Thu, Jun 25, 2009 at 11:37 AM, Bill Moran >wrote:
> >
> > > In response to Jack W :
> > >
> > > > I will create several databases on PostGreSQL. All the databases have
> the
> > > > same structure: same number
In response to Jack W :
> On Thu, Jun 25, 2009 at 11:37 AM, Bill Moran wrote:
>
> > In response to Jack W :
> >
> > > I will create several databases on PostGreSQL. All the databases have the
> > > same structure: same number of table/index.
> > > I have two choices:
> > > 1. For each database, I
In response to Jack W :
> I will create several databases on PostGreSQL. All the databases have the
> same structure: same number of table/index.
> I have two choices:
> 1. For each database, I create a new tablespace and create a new database in
> the tablespace.
> 2. I only create one tablespace
I will create several databases on PostGreSQL. All the databases have the
same structure: same number of table/index.
I have two choices:
1. For each database, I create a new tablespace and create a new database in
the tablespace.
2. I only create one tablespace. Create all the databases on the sam
