| From: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
|---|---|
| To: | Michael Stone <mstone+postgres(at)mathom(dot)us> |
| Cc: | pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: Some performance numbers, with thoughts |
| Date: | 2006-06-27 07:12:50 |
| Message-ID: | 1151392370.2479.150.camel@localhost.localdomain |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Mon, 2006-06-26 at 17:20 -0400, Michael Stone wrote:
> On Mon, Jun 26, 2006 at 08:33:34PM +0100, Simon Riggs wrote:
> >of the SQL standard, so being unaware of them when using SQL is strange
> >to me.
>
> Welcome to the world of programs designed for mysql. You'll almost never
> see them batch inserts, take advantage of referential integrity, etc.
> You end up with lots of selects & inserts in loops that expect
> autocommit-like behavior because it doesn't matter in that world.
Yes, I suspected that was the case. I was interested in understanding
why anybody thought it was acceptable, and in what conditions that might
be the case. Brian's open approach has helped explain things for me.
--
Simon Riggs
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Sagulin | 2006-06-27 12:14:08 | Large index scan perfomance and indexCorrelation (PG 8.1.4 Win32) |
| Previous Message | Diego Gaviola | 2006-06-26 22:44:57 | unsubscribe |