On 2011-08-12, at 10:10 , Kevin Grittner wrote:
> Turning fsync off in production may be OK as long as those daily
> backups aren't in the same building as the uber expensive SAN, and
> it's really OK to fall back on a daily backup if the database server
> crashes or locks up. By the way, I neve
On 2011-08-12, at 09:32 , Merlin Moncure wrote:
> In my opinion before looking at postgresql.conf you need to make sure
> your queries and their plans are good. fire up pgfouine and see where
> those 60 minutes are gettings spent. maybe you have a problem query
> that demands optimization.
Tha
On 2011-08-12, at 03:58 , jenopob wrote:
>
> I do some db falt tests
> 1)the test code run always connect pgpool,
> 2)test master or slave go down
>
> but when mster or slave go down ,java code throws exception :
>
> org.postgresql.util.PSQLException: An I
On 2011-08-11, at 18:17 , Greg Smith wrote:
> shared_buffers=512MB
> wal_buffers=16MB
> checkpoint_segments=64
Thanks for the advice. I tried these values... And it is even worse - went up
to 63 minutes (from 60 minutes). Like I said this load is read mostly. My 80
/ 20% might be a bit inac
On 2011-08-11, at 17:18 , k...@rice.edu wrote:
> One guess is that you are using the defaults for other costing parameters and
> they
> do not accurately reflect your system. This means that it will be a crap
> shoot as
> to whether a plan is faster or slower and what will affect the timing.
O
I have PostgreSQL 8.4.8 on Ubuntu Linux x64. Server is a Core i7 950 with 6GB
of RAM. 2GB of RAM us used by Java, some small amount by the kernel / services
and the rest is available to PostgreSQL. Hard drive is a single 7200 RPM SATA
1TB Caviar Black HDD. No other applications / processes a
I have PostgreSQL 8.4.8 on Ubuntu Linux x64. Server is a Core i7 950 with 6GB
of RAM. 2GB of RAM us used by Java, some small amount by the kernel / services
and the rest is available to PostgreSQL. Hard drive is a single 7200 RPM SATA
1TB Caviar Black HDD. No other applications / processes a
