>>> Alexander Staubo wrote:
> Kevin Grittner wrote:
>> Could you show the non-commented lines from old and new
>> postgresql.conf files, please?
>
> Attached. The differences are not performance-related, as far as I
> can see, aside from the additional of "synchronous_commit = off".
You shoul
Teodor Sigaev writes:
>> seems to me that we ought to get rid of intarray's @> and <@ operators
>> and have the module depend on the core anyarray operators, just as we
>> have already done for = and <>. Comments?
> Agree, will do. Although built-in anyarray operators have ~N^2 behaviour
> whil
On Fri, Feb 13, 2009 at 5:17 PM, Kevin Grittner
wrote:
> Could you show the non-commented lines from old and new
> postgresql.conf files, please?
Attached. The differences are not performance-related, as far as I can
see, aside from the additional of "synchronous_commit = off".
Alexander.
82.c
>>> Alexander Staubo wrote:
> When I compare the correct graph, however, it's apparently that I/O
> writes have, on average, doubled.
Could you show the non-commented lines from old and new
postgresql.conf files, please?
-Kevin
--
Sent via pgsql-performance mailing list (pgsql-performance@p
On Fri, Feb 13, 2009 at 12:53 PM, Alexander Staubo wrote:
> The upgrade was done with dump/restore using "pg_dump -Fc". The old
> database lived on a SAN volume, whereas the new database lives on a
> local disk volume.
I need to correct myself: The Munin graphs were never set to track the
SAN vol
On Fri, Feb 13, 2009 at 3:46 PM, Kevin Grittner
wrote:
Alexander Staubo wrote:
>> After upgrading from 8.2 to 8.3.5, the write load on our database
>> server has increased dramatically and inexplicably -- as has the CPU
>> usage.
>
> Did you do a VACUUM ANALYZE of the database after loading
>>> Alexander Staubo wrote:
> After upgrading from 8.2 to 8.3.5, the write load on our database
> server has increased dramatically and inexplicably -- as has the CPU
> usage.
Did you do a VACUUM ANALYZE of the database after loading it? Without
the database VACUUM, the first read of any page
On Fri, 13 Feb 2009, Rajesh Kumar Mallah wrote:
I have received Dell Poweredge 2950 MIII with 2 kind of
drives. I cant' make out the reason behind it , does it
make any difference in long run or in performance
the drives are similar in overall characteristics but does
the minor differences if wil
On Fri, Feb 13, 2009 at 04:12:53PM +0300, Teodor Sigaev wrote:
>> The short-term workaround for Rusty is probably to create his GIN
>> index using the intarray-provided gin__int_ops opclass. But it
> Right
>> seems to me that we ought to get rid of intarray's @> and <@ operators
>> and have the mo
I have received Dell Poweredge 2950 MIII with 2 kind of
drives. I cant' make out the reason behind it , does it
make any difference in long run or in performance
the drives are similar in overall characteristics but does
the minor differences if will cause any problem ?
scsi0 : LSI Logic SAS based
After upgrading from 8.2 to 8.3.5, the write load on our database
server has increased dramatically and inexplicably -- as has the CPU
usage.
Here's a Munin graph of iostat showing the sudden increase in blocks
written/sec:
http://purefiction.net/paste/Totals-iostatwrite1-week.png
We expected
11 matches
Mail list logo
