| Lists: | pgsql-hackers |
|---|
| From: | wade <wade(at)wavefire(dot)com> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | POSIX regex performance bug in 7.3 Vs. 7.2 |
| Date: | 2003-01-31 22:37:00 |
| Message-ID: | 3.0.32.20030131143700.01ca3b50@mail.wavefire.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Lists: | pgsql-hackers |
Hello,
We recently upgraded a project from 7.2 to 7.3.1 to make use of some of
the cool new features in 7.3. The installed version is CVS stable from
yesterday. However, we noticed a major performance hit in POSIX regular
expression matches against columns using the ~* operator.
http://arch.wavefire.com/badregex73.txt has explain analyze output from 7.2
and 7.3.1 respectively. Both of these tables have only 101 rows. The
7.3.1 install is using the default settings from postgresql.conf.
Any ideas as to why this should be happening?
Should anyone require additional information, please let me know.
-Wade Klaver
| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | wade <wade(at)wavefire(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: POSIX regex performance bug in 7.3 Vs. 7.2 |
| Date: | 2003-02-01 03:52:53 |
| Message-ID: | 4007.1044071573@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Lists: | pgsql-hackers |
wade <wade(at)wavefire(dot)com> writes:
> We recently upgraded a project from 7.2 to 7.3.1 to make use of some of
> the cool new features in 7.3. The installed version is CVS stable from
> yesterday. However, we noticed a major performance hit in POSIX regular
> expression matches against columns using the ~* operator.
The only thought that comes to mind is that multibyte character sets are
supported in 7.3 whereas they were optional (and not default) in 7.2.
I'd not have expected a factor-of-150 performance hit from that, though.
Could you rebuild your backend with profiling enabled and get a gprof
summary of where the time is going?
regards, tom lane
| From: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> |
|---|---|
| To: | wade <wade(at)wavefire(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: POSIX regex performance bug in 7.3 Vs. 7.2 |
| Date: | 2003-02-01 12:31:05 |
| Message-ID: | 20030201203052.C32061-100000@houston.familyhealth.com.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Lists: | pgsql-hackers |
Why on earth are you using a CVS version!?!?!?!
Chris
On Fri, 31 Jan 2003, wade wrote:
> Hello,
> We recently upgraded a project from 7.2 to 7.3.1 to make use of some of
> the cool new features in 7.3. The installed version is CVS stable from
> yesterday. However, we noticed a major performance hit in POSIX regular
> expression matches against columns using the ~* operator.
> http://arch.wavefire.com/badregex73.txt has explain analyze output from 7.2
> and 7.3.1 respectively. Both of these tables have only 101 rows. The
> 7.3.1 install is using the default settings from postgresql.conf.
>
> Any ideas as to why this should be happening?
>
> Should anyone require additional information, please let me know.
>
> -Wade Klaver
>
> ---------------------------(end of broadcast)---------------------------
> TIP 5: Have you checked our extensive FAQ?
>
> http://www.postgresql.org/users-lounge/docs/faq.html
>
| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> |
| Cc: | wade <wade(at)wavefire(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: POSIX regex performance bug in 7.3 Vs. 7.2 |
| Date: | 2003-02-01 16:41:32 |
| Message-ID: | 7499.1044117692@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Lists: | pgsql-hackers |
Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> writes:
> Why on earth are you using a CVS version!?!?!?!
I assume he meant tip of REL7_3 branch --- which is a perfectly
reasonable thing to install, even if there are still a few fixes
to go before we call it 7.3.2.
regards, tom lane