Re: [PERFORM] query not using index

2013-12-23 Thread Johann Spies
On 19 December 2013 16:48, Tom Lane t...@sss.pgh.pa.us wrote: Johann Spies johann.sp...@gmail.com writes: I would appreciate some help optimising the following query: It's a mistake to imagine that indexes are going to help much with a join of this size. Hash or merge join is going to be a

Re: [PERFORM] slow query - will CLUSTER help?

2013-12-23 Thread Shaun Thomas
What are your thoughts on the right way to use SSDs in a RAID to enhance postgres I/O performance? In an earlier reply, you indicated one of a RAID1+0 consisting of several spindles, NVRAM-based solution (SSD or PCIe card), or a SAN Well, it's a tiered approach. If you can identify your

[PERFORM] Bytea(TOAST) vs large object facility(OID)

2013-12-23 Thread kosalram Babu Chellappa
Hi,  We have a requirement to store images/documents with an average size of 1-2MB on PostgreSQL database. We have PostgreSQL 9.2.4 running on Red hat linux 64 bit. We decided to setup a stand alone postgreSQL server without streaming replication to host the images/documents only. We are new to

Re: [PERFORM] Optimizing a query

2013-12-23 Thread Mark Kirkwood
On 20/12/13 06:53, Shaun Thomas wrote: On 12/17/2013 08:48 PM, Kai Sellgren wrote: This is your select: SELECT * FROM Log LEFT JOIN NewsArticle ON NewsArticle.id = Log.targetId AND Log.targetType = 'NewsArticle' ORDER BY Log.createdAt DESC LIMIT 10 This is your index: CREATE INDEX

Re: [PERFORM] Bytea(TOAST) vs large object facility(OID)

2013-12-23 Thread Albe Laurenz
kosalram Babu Chellappa wrote: We have a requirement to store images/documents with an average size of 1-2MB on PostgreSQL database. We have PostgreSQL 9.2.4 running on Red hat linux 64 bit. We decided to setup a stand alone postgreSQL server without streaming replication to host the