ned tables
tend to be huge almost by definition.
Offhand, it would seem that this would be a feature largely restricted
to threaded database kernels for a couple different pragmatic reasons.
Cheers,
-James Rogers
[EMAIL PROTECTED]
---(end of broadcast)---
I've
found. A lot of scalability is how you set the parameters and design
the system if the underlying engine is reasonably competent. For the
vast majority of purposes, you'll find that PostgreSQL scales just fine.
Cheers,
-James Rogers
[EMAIL PROTECTED]
--
add that I don't know what PostgreSQL actually does in this regard, but
from the thread it appears as though seqscans are handled like the
default case.
Cheers,
-James Rogers
[EMAIL PROTECTED]
---(end of broadcast)---
TIP 3: if posting/rea
need to understand the
limitations, nonetheless when tables and databases get really big it becomes
an important tool in the tool belt.
Cheers,
-James Rogers
[EMAIL PROTECTED]
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
