Chris Barnes wrote:
>> Does anyone use solid state drives for postgres?
>> Has there been any benchmark that states whether mechanical disk drives out
>> perform solid state drives?
>> Is there any benefit, they are quite expensive.
I am currently running PostgreSQL 8.4.1 on a Mac Pro 2009 with
I just got this error, and I don't know why I got it:
7/12/09 2:57:24 PMorg.postgresql.postgres[89]ERROR: could not
access status of transaction 825832753
7/12/09 2:57:24 PMorg.postgresql.postgres[89]DETAIL: Could not open
file "pg_clog/0313": No such file or directory.
7/12/09 2
I've been trying to track down a performance issue I have. In simple terms,
my select performance is very good (generally either CPU limited, or disk
limited, depending upon the query), and small updates seem OK.
But a huge UPDATE is incredibly slow. CPU is on average below 1%, and disk
IO is ge
On Wed, Dec 9, 2009 at 12:57 PM, Greg Smith wrote:
> You should turn on log_checkpoint in the postgresql.conf and confirm the
> slowdowns are happening around the same time as the checkpoint report gets
> written to the log files.
Thank you for your suggestions. I will turn on log_checkpoint n
Some more information on fsync using the test_fsync tool in
postgres/src/tools:
System is Snow Leopard 10.6.2 (64 bit). Volumes are HFS+ formatted.
PASS 1 - DATABASE VOLUME (SSD RAID 0)
===
$ sudo ./test_fsync -f /Volumes/SSD/fsync_test.out
Simple write timing:
On Thu, Dec 10, 2009 at 8:38 AM, Greg Smith wrote:
> PostgreSQL on OS X uses a special fsync method by default named
> 'fsync_writethrough'. If you do this on your database you should be able to
> confirm it's using it:
>
> show wal_sync_method;
>
> This method includes a call to Apple's API to
On Wed, Dec 9, 2009 at 12:57 PM, Greg Smith wrote:
> You should turn on log_checkpoint in the postgresql.conf and confirm the
> slowdowns are happening around the same time as the checkpoint report gets
> written to the log files.
I have turned on log_checkpoints, and re-run the command. Check
On Thu, Dec 10, 2009 at 9:21 PM, Stephen Tyler wrote:
> I have turned on log_checkpoints, and re-run the command. Checkpoints are
> being written every 220 to 360 seconds. About 80% are "time" and 20%
> "xlog". Here are a representative sa
