Re: [PERFORM] File Systems Compared

2006-12-17 Thread Bruno Wolff III
On Fri, Dec 15, 2006 at 10:44:39 -0600, Bruno Wolff III [EMAIL PROTECTED] wrote: The other feature I would like is to be able to use write barriers with encrypted file systems. I haven't found anythign on whether or not there are near term plans by any one to support that. I asked about

Re: [PERFORM] Scaling concerns

2006-12-17 Thread Bill Moran
tsuraan [EMAIL PROTECTED] wrote: I'm writing a webmail-type application that is meant to be used in a corporate environment. The core of my system is a Postgres database that is used as a message header cache. The two (relevant) tables being used are pasted into the end of this message. My

Re: [PERFORM] Scaling concerns

2006-12-17 Thread tsuraan
To quickly find out a subset of slow queries on your production system, you can use the pgfouine tool: http://pgfouine.projects.postgresql.org/ If you then want to make some measurements of PostgreSQL performances with some different settings and compare them, consider using the tsung tool

Re: [PERFORM] Scaling concerns

2006-12-17 Thread tsuraan
For scaling you should consider slony. Either hangout on #slony on Freenode.net or ask on the mailing list if you have questions. For some reason I had thought slony was really immature, but it actually looks really usable. Intel chips = define more. There are Intel boxes known to have issues

Re: [PERFORM] Scaling concerns

2006-12-17 Thread Greg Smith
On Sun, 17 Dec 2006, tsuraan wrote: Since my application is constantly adding to the database (far more is written than is ever read), it would be nice to have a multiple-write, single reader solution, if such a thing exists. You seem to be working from the assumption that you have a scaling

Re: [PERFORM] Scaling concerns

2006-12-17 Thread tsuraan
http://www.powerpostgresql.com/Downloads/annotated_conf_80.html is a good intro to the various parameters you might set, with some valuable hints on the effective range you should be considering. I'd suggest you use that to identify the most likely things to increase, then read the manuals at

Re: [PERFORM] Scaling concerns

2006-12-17 Thread Tom Lane
tsuraan [EMAIL PROTECTED] writes: Is the WAL at the same location as the xlog (transaction log?)? Same thing. The checkpoint_segments doc says increasing that value is really only useful if the xlog is separate from the data, Dunno where you read that, but it's utter bilge. If you've got a

[PERFORM] Optimizing timestamp queries? Inefficient Overlaps?

2006-12-17 Thread Adam Rich
I have a table similar to this: CREATE TABLE event_resources ( event_resource_id serial NOT NULL, event_id integer NOT NULL, resource_id integer NOT NULL, start_date timestamptz NOT NULL, end_date timestamptz NOT NULL, CONSTRAINT event_resources_pkey PRIMARY KEY

Re: [PERFORM] Optimizing timestamp queries? Inefficient Overlaps?

2006-12-17 Thread Tom Lane
Adam Rich [EMAIL PROTECTED] writes: I have a table similar to this: CREATE TABLE event_resources ( event_resource_id serial NOT NULL, event_id integer NOT NULL, resource_id integer NOT NULL, start_date timestamptz NOT NULL, end_date timestamptz NOT NULL,