From: | Alex Pilosov <alex(at)pilosoft(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: PostgreSQL profiling? |
Date: | 2001-02-04 15:39:14 |
Message-ID: | Pine.BSO.4.10.10102040002260.10437-100000@spider.pilosoft.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Thanks Tom.
I think that in future, locale setting should be a disclosed part of
benchmark results whenever PostgreSQL is benchmarked.
-alex
On Sat, 3 Feb 2001, Tom Lane wrote:
> Alex Pilosov <alex(at)pilosoft(dot)com> writes:
> > Have someone made effort to do profiling of pgsql during execution of
> > certain things (inserts, selects, sorting, indices)?
>
> Yes ...
>
> > I have a feeling (based on stopping postgres from gdb periodically), that
> > a lot of time is used in strcoll() (if table and index has string
> > columns).
> > Column in question is declared char(3).
> > So, why's postgres collating anything at all?
>
> Because textual comparisons are defined in terms of strcoll() if you've
> enabled locale support. There is no way around this; either don't use
> locales or write a faster version of strcoll().
>
> regards, tom lane
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Ian deSouza | 2001-02-04 16:04:07 | Problem when calling setObject on Timestamp column with JDBC driver |
Previous Message | Brett W. McCoy | 2001-02-04 14:19:40 | Re: outer joins |