Hey Everyone,
So, I have a nice postgreSQL server (8.4) up and running our
database. I even managed to get master->slave going without trouble
using the excellent skytools.. however, I want to maximize speed and the
hot updates where possible, so, I am wanting to prune unused indexes
from t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Stef Telford wrote:
> Stef Telford wrote:
>> Mark Kirkwood wrote:
>>> Scott Carey wrote:
>>>> A little extra info here >> md, LVM, and some other tools do
>>>> not allow the file system to use write ba
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Stef Telford wrote:
> Mark Kirkwood wrote:
>> Scott Carey wrote:
>>> A little extra info here >> md, LVM, and some other tools do
>>> not allow the file system to use write barriers properly So
>>> th
Matthew Wakeling wrote:
> On Wed, 1 Apr 2009, Stef Telford wrote:
>>Good UPS, a warm PITR standby, offsite backups and regular checks is
>> "good enough" for me, and really, that's what it all comes down to.
>> Mitigating risk and factors into an 'accep
Scott Marlowe wrote:
> On Wed, Apr 1, 2009 at 10:15 AM, Stef Telford wrote:
>
>> I do agree that the benefit is probably from write-caching, but I
>> think that this is a 'win' as long as you have a UPS or BBU adaptor,
>> and really, in a prod enviro
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Greg Smith wrote:
> On Wed, 1 Apr 2009, Stef Telford wrote:
>
>> I have -explicitly- enabled sync in the conf...In fact, if I turn
>> -off- sync commit, it gets about 200 -slower- rather than
>> faster.
>
> Yo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mark Kirkwood wrote:
> Scott Carey wrote:
>>
>> A little extra info here >> md, LVM, and some other tools do not
>> allow the file system to use write barriers properly So
>> those are on the bad list for data integrity with SAS or SATA
>> write
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mark Kirkwood wrote:
> I'm trying to pin down some performance issues with a machine where
> I work, we are seeing (read only) query response times blow out by
> an order of magnitude or more at busy times. Initially we blamed
> autovacuum, but after
