tablespaces in 7.5?

[Brian Maguire]

I am curious if tablespaces are going to be seriously targeted for the next version. It really opens up new levels of scalability and is a killer feature from an administration perspective.

Thanks,

Brian


---------------------------(end of broadcast)---------------------------TIP 9: the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match

[Bruce Momjian]

Brian Maguire wrote:

I am curious if tablespaces are going to be seriously targeted
for the next version. It really opens up new levels of scalability
and is a killer feature from an administration perspective.

I hope so!

--
Bruce Momjian | http://candle.pha.pa.us
pg***@candle.pha.pa.us | [phone]
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073

---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to ma*******@postgresql.org so that your
message can get through to the mailing list cleanly

[Keith C. Perry]

Quoting Bruce Momjian <pg***@candle.pha.pa.us>:

Brian Maguire wrote:

I am curious if tablespaces are going to be seriously targeted
for the next version. It really opens up new levels of scalability
and is a killer feature from an administration perspective.

I hope so!

--
Bruce Momjian | http://candle.pha.pa.us
pg***@candle.pha.pa.us | [phone]
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073

---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to ma*******@postgresql.org so that your
message can get through to the mailing list cleanly

Excuse my ignorance but what will namespaces give us? I though PG schema
provided the namespace functionality- 'least the way I am understanding the term.

--
Keith C. Perry, MS E.E.
Director of Networks & Applications
VCSN, Inc.
http://vcsn.com

____________________________________
This email account is being host by:
VCSN, Inc : http://vcsn.com

---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match

[John Sidney-Woollett]

My (limited) understanding is that it will give you the ability to:

i) decide what data resides in what tablespace, (database, schema,
indexes, data [coarser -> finer grain]).
ii) where the tablespace data is physically located, allowing you to
distribute your database across disks, or disk arrays.

John Sidney-Woollett

Keith C. Perry said:

Quoting Bruce Momjian <pg***@candle.pha.pa.us>:

Brian Maguire wrote:

> I am curious if tablespaces are going to be seriously targeted
> for the next version. It really opens up new levels of scalability
> and is a killer feature from an administration perspective.

I hope so!

--
Bruce Momjian | http://candle.pha.pa.us
pg***@candle.pha.pa.us | [phone]
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania
19073

---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to ma*******@postgresql.org so that your
message can get through to the mailing list cleanly

Excuse my ignorance but what will namespaces give us? I though PG schema
provided the namespace functionality- 'least the way I am understanding
the term.

--
Keith C. Perry, MS E.E.
Director of Networks & Applications
VCSN, Inc.
http://vcsn.com

____________________________________
This email account is being host by:
VCSN, Inc : http://vcsn.com

---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match

---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match