unsubscribe
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
On Mon, 2006-06-19 at 20:09 -0400, Brian Hurt wrote:
> 5) The performance of Postgres, at least on inserts, depends critically
> on how you program it. One the same hardware, performance for me varied
> over a factor of over 300-fold, 2.5 orders of magnitude. Programs which
> are unaware of tr
Thank you for you quick answer i will try to see what i can do whith the file
contrib/pgstattuple
Best regards,
> Message du 23/06/06 à 18h11
> De : "Tom Lane" <[EMAIL PROTECTED]>
> A : [EMAIL PROTECTED]
> Copie à : pgsql-performance@postgresql.org
> Objet : Re: [PERFORM] Occupation bloc in pag
> De : "Tom Lane" <[EMAIL PROTECTED]>
> There is not any magic way of getting that information, but you could
> modify contrib/pgstattuple to produce such a report.
Thank you for you speed answer , i will try to see what i can do in
contrib/pgstattuple
Best regards,
Luc
---
Tom,
thank you.
> I think the problem is probably that you're sorting two dozen CHAR
> columns, and that in many of the rows all these entries are '' forcing
> the sort code to compare all two dozen columns (not so)? So the sort
> ends up doing lots and lots and lots of CHAR comparisons. Which
Thank you for you quick answer i will try to see what i can do whith the file
contrib/pgstattuple
Best regards,
> Message du 23/06/06 à 18h11
> De : "Tom Lane" <[EMAIL PROTECTED]>
> A : [EMAIL PROTECTED]
> Copie à : pgsql-performance@postgresql.org
> Objet : Re: [PERFORM] Occupation bloc in page
