Rusty
Scott Marlowe wrote:
On Thu, Jan 15, 2009 at 2:55 PM, Bill Preston
wrote:
Nothing special about that table. One index.
It really seems that the system would grind to a stand-still when a lot of
non-transaction inserts were run combined with the creation of some large
temp tables.
Sin
nicely. The suggestions here really helped.
Does anyone know of some established postgresql consultants that can be
hired for emergency analysis/tuning when things come up?
Rusty
Alan Hodgson wrote:
On Monday 12 January 2009, Bill Preston
wrote:
As to the second example with the delete. There
nuary 2009, Bill Preston
wrote:
I had a data load that I was doing with 8.1. It involved about 250k sql
statements that were inserts into a table with just one index. The index
has two fields.
With the upgrade to 8.3 that process started taking all night and 1/2 a
day. It inserted at the r
Hi Group.
Recently upgraded from 8.1 to 8.3 on RHEL 5 64-bit.
I've noticed some performance problems that I am guessing are WAL
related based on my browsing around and wondered if someone had some
suggestions for tuning the WAL settings. It could also help if someone
just laughed at me and tol
