Re: [PERFORM] Re: How to track number of connections and hosts to Postgres cluster

2011-09-01 Thread Scott Marlowe
On Thu, Sep 1, 2011 at 11:46 PM, Venkat Balaji wrote: > Hi Scott, > Log generation rate - > 500MB size of log file is generated within minimum 3 mins to maximum of 20 > mins depending on the database behavior. > I did not understand the "fsync" stuff you mentioned. Please help me know > how would

Re: [PERFORM] Re: How to track number of connections and hosts to Postgres cluster

2011-09-01 Thread Venkat Balaji
Hi Scott, Log generation rate - 500MB size of log file is generated within minimum 3 mins to maximum of 20 mins depending on the database behavior. I did not understand the "fsync" stuff you mentioned. Please help me know how would fsync is related to log generation or logging host IPs in the lo

Re: [PERFORM] Summaries on SSD usage?

2011-09-01 Thread Scott Marlowe
On Tue, Aug 30, 2011 at 11:23 AM, Stefan Keller wrote: > Hi, > > I'm looking for summaries (or best practices) on SSD usage with PostgreSQL. > My use case is mainly a "read-only" database. > Are there any around? How big is your DB? What kind of reads are most common, random access or sequential?

Re: [PERFORM] Summaries on SSD usage?

2011-09-01 Thread Jesper Krogh
On 2011-09-01 23:28, Jim Nasby wrote: On Aug 30, 2011, at 12:23 PM, Stefan Keller wrote: I'm looking for summaries (or best practices) on SSD usage with PostgreSQL. My use case is mainly a "read-only" database. Are there any around? I'm not sure, but for read-only why not just put more memory i

Re: [PERFORM] 8.4 optimization regression?

2011-09-01 Thread Mark Kirkwood
On 02/09/11 11:18, Mark Kirkwood wrote: On 02/09/11 11:13, Tom Lane wrote: I wrote: Mark Kirkwood writes: [ assorted examples showing that commit 7f3eba30c9d622d1981b1368f2d79ba0999cdff2 has got problems ] ... So, not only are you correct that we should revert the changes to eqjoinsel_inner,

Re: [PERFORM] Summaries on SSD usage?

2011-09-01 Thread Stefan Keller
You mean something like "Unlogged Tables" in PostgreSQL 9.1 (= in-memory database) or simply a large ramdisk? Yours, Stefan 2011/9/1 Jim Nasby : > On Aug 30, 2011, at 12:23 PM, Stefan Keller wrote: >> I'm looking for summaries (or best practices) on SSD usage with PostgreSQL. >> My use case is ma

Re: [PERFORM] 8.4 optimization regression?

2011-09-01 Thread Mark Kirkwood
On 02/09/11 11:13, Tom Lane wrote: I wrote: Mark Kirkwood writes: [ assorted examples showing that commit 7f3eba30c9d622d1981b1368f2d79ba0999cdff2 has got problems ] ... So, not only are you correct that we should revert the changes to eqjoinsel_inner, but what's happening in eqjoinsel_semi i

Re: [PERFORM] Summaries on SSD usage?

2011-09-01 Thread Jim Nasby
On Aug 30, 2011, at 12:23 PM, Stefan Keller wrote: > I'm looking for summaries (or best practices) on SSD usage with PostgreSQL. > My use case is mainly a "read-only" database. > Are there any around? I'm not sure, but for read-only why not just put more memory in the server? It'll be a lot cheap

Re: [PERFORM] 8.4 optimization regression?

2011-09-01 Thread Tom Lane
I wrote: > Mark Kirkwood writes: >> [ assorted examples showing that commit >> 7f3eba30c9d622d1981b1368f2d79ba0999cdff2 has got problems ] > ... > So, not only are you correct that we should revert the changes to > eqjoinsel_inner, but what's happening in eqjoinsel_semi is wrong too. I've retest

Re: [PERFORM] issue related to logging facility of postgres

2011-09-01 Thread Justin Pitts
Syslog does that, I believe. Have a look at the man page for syslog.conf. On Wed, Jul 27, 2011 at 5:11 AM, shailesh singh wrote: > Hi, > I want to configure Logging of postgres in such a way that messages of > different severity should be logged in different log file. eg: all ERROR > message shou