You can find a diagram of my initial
spec here:
http://img266.imageshack.us/img266/9171/dbserverdiagramuc3.jpg
Can you guys see any glaring bottlenecks in my layout?
Any other suggestions to offer (throw in more
controllers, different RAID layout, etc.)? Our budget
limit is $50k.
The thing I
> I heard some say that the transaction log should be on
> it's own array, others say it doesn't hurt to have it
> on the same array as the OS. Is it really worthwhile
> to put it on it's own array?
>
> Can you guys see any glaring bottlenecks in my layout?
> Any other suggestions to offer (thr
> Yeah, but they had to back-off from that plan, and AFAIK it only uses
> libpq for the auth stuff and then switch to dealing with the protocol
> directly.
>
> I don't know what the reasoning was though :-) I guess Joshua would
> know. I'm not involved in that project. I only know that recentl
Merlin Moncure wrote:
> On 10/21/06, Alvaro Herrera <[EMAIL PROTECTED]> wrote:
> >Try Command Prompt's ODBC driver. Lately it has been measured to be
> >consistently faster than psqlODBC.
> >
> >http://projects.commandprompt.com/public/odbcng
>
> just curious: what was the reasoning to reimpleme
Hello,
I'm working out specs for a new database server to be
purchased for our organization. The applications the
server will handle are mainly related to network
operations (monitoring, logging, statistical/trend
reports, etc.). Disk I/O will be especially high with
relation to processing netwo
> carlo: please, please, get your mail server to quit telling me your
> mailbox is full :)
Merlin, sorry about that. This is the first I've heard of it.
Carlo
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
> Hello Performancers,
>
> has anyone a pgBench tool running on Windows?
Does the one that ships in the installer not work?
//Magnus
---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs
Sorry for the amateurish question, but what are "heap tuples"?
Also, my understanding is that the following statement applies only for
composite indexes: "PostgreSQL can't use the values stored in the index
to check the join condition". I assume that PostgreSQL will be able to
use single-colum
