On Wed, 2008-01-09 at 10:18 +0200, Adrian Moisey wrote:
> We recently converted to postgres (from mssql) and we're having
> performance issues.
I think you need to say more about what the performance issues actually
are, otherwise everybody will just speculate you to death.
--
Simon Riggs
On Wed, 9 Jan 2008, Guillaume Smet wrote:
On Jan 9, 2008 9:27 AM, Joshua D. Drake <[EMAIL PROTECTED]> wrote:
wal_sync_method = open_sync
Do you recommend it in every situation or just because data are on a
SAN? Do you have any numbers/real cases explaining this choice.
Sync writes are faste
On Jan 9, 2008, at 12:00 AM, Anoo Sivadasan Pillai wrote:
Why the procedure is not getting the performance advantage of Vacuum
analyse?
Plan caching by the function, probably. Try disconnecting the
session
and reconnecting to prove the hypothesis.
If it is a recurring problem for you
On Wed, Jan 09, 2008 at 12:27:33AM -0800, Joshua D. Drake wrote:
> Adrian Moisey wrote:
>> Hi
>>
>> We recently converted to postgres (from mssql) and we're having
>> performance issues. Not all the issues are related to postgres, but we're
>> trying to sort everything out.
Hi,
Hi Joshua,
On Jan 9, 2008 9:27 AM, Joshua D. Drake <[EMAIL PROTECTED]> wrote:
> wal_sync_method = open_sync
Do you recommend it in every situation or just because data are on a
SAN? Do you have any numbers/real cases explaining this choice.
Thanks.
--
Guillaume
---(end
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, 9 Jan 2008 08:16:48 -0800
Alan Hodgson <[EMAIL PROTECTED]> wrote:
> On Wednesday 09 January 2008, Adrian Moisey
> <[EMAIL PROTECTED]> wrote:
> >
> > Also, we're running the db on ext3 with noatime. Should I look at
> > changing or getting ri
On Wednesday 09 January 2008, Adrian Moisey <[EMAIL PROTECTED]>
wrote:
>
> Also, we're running the db on ext3 with noatime. Should I look at
> changing or getting rid of journaling ?
No (unless you like really long fsck times). data=writeback is safe with
PostgreSQL, though.
Hi
We recently converted to postgres (from mssql) and we're having
performance issues. Not all the issues are related to postgres, but
we're trying to sort everything out.
The server is running ubuntu Gutsy with the database stored on a IBM
SAN. It is a Dell box with dual quad core 2.00GHz
Did you try integer arrays with GIN (inverted index) ?
Oleg
On Wed, 9 Jan 2008, J?rg Kiegeland wrote:
Hello,
I have an interesting generic search task, for which I have done different
performance tests and I would like to share and discuss my results on this
newsgroup.
So I begin to descri
Hello,
I have an interesting generic search task, for which I have done
different performance tests and I would like to share and discuss my
results on this newsgroup.
So I begin to describe the search task:
=
You have a set of N unique IDs. Every ID is associated with an integer
sc
Hi,
what segment size do you use for the san partition? This could also be a
bottle neck for db servers.
Frank
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
Adrian Moisey wrote:
Hi
We recently converted to postgres (from mssql) and we're having
performance issues. Not all the issues are related to postgres, but
we're trying to sort everything out.
The server is running ubuntu Gutsy with the database stored on a IBM
SAN. It is a Dell box with
Hi
We recently converted to postgres (from mssql) and we're having
performance issues. Not all the issues are related to postgres, but
we're trying to sort everything out.
The server is running ubuntu Gutsy with the database stored on a IBM
SAN. It is a Dell box with dual quad core 2.00GHz
13 matches
Mail list logo
