We run GCC-compiled postgresql on a number
of HP-UX and Linux boxes.
Our measurements to date show 8.3.1
performance to be about 30% *worse*
than 8.2 on HP-UX for the same "drink the firehose"
insert/update/delete benchmarks. Linux
performance is fine.
Tweaking the new 8.3.1 synchronous_commit
On Wed, Jun 11, 2008 at 3:56 AM, Zoltan Boszormenyi <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I got a question about scalability in high volume insert situation
> where the table has a primary key and several non-unique indexes
> on other columns of the table. How does PostgreSQL behave
> in terms of sc
Zoltan Boszormenyi wrote:
> Hi,
>
> I got a question about scalability in high volume insert situation
> where the table has a primary key and several non-unique indexes
> on other columns of the table. How does PostgreSQL behave
> in terms of scalability? The high volume of inserts comes from
> m
[EMAIL PROTECTED] írta:
>> Hi,
>>
>> I got a question about scalability in high volume insert situation
>> where the table has a primary key and several non-unique indexes
>> on other columns of the table. How does PostgreSQL behave
>> in terms of scalability? The high volume of inserts comes from
> Hi,
>
> I got a question about scalability in high volume insert situation
> where the table has a primary key and several non-unique indexes
> on other columns of the table. How does PostgreSQL behave
> in terms of scalability? The high volume of inserts comes from
> multiple transactions.
>
> B
Hi,
I got a question about scalability in high volume insert situation
where the table has a primary key and several non-unique indexes
on other columns of the table. How does PostgreSQL behave
in terms of scalability? The high volume of inserts comes from
multiple transactions.
Best regards,
Zol
