From: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
---|---|
To: | Marc Mamin <M(dot)Mamin(at)intershop(dot)de> |
Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
Subject: | Re: PostgreSQL SQL Tricks: faster urldecode |
Date: | 2013-09-20 15:43:56 |
Message-ID: | CAHyXU0wryo-xghazx_Ww5hGq3m1G8Mm2E+fDGUxH8__MwZ9qjA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Fri, Sep 20, 2013 at 10:26 AM, Marc Mamin <M(dot)Mamin(at)intershop(dot)de> wrote:
> Hi,
> here is a function which is about 8 x faster than the one described in the PostgreSQL SQL Tricks
> ( http://postgres.cz/wiki/PostgreSQL_SQL_Tricks#Function_for_decoding_of_url_code )
>
> The idea is to handle each encoded/not_encoded parts in bulk rather than spliting on each character.
>
> urldecode_arr:
> Seq Scan on lt_referrer (actual time=1.966..17623.979 rows=65717 loops=1)
>
> urldecode:
> Seq Scan on lt_referrer (actual time=4.846..144445.292 rows=65717 loops=1)
very nice. Basically it comes down to this: all non-trivial regex
replacements require decomposition of the string into an array because
regexp_replace() is unable to do any kind of transformation on the
string. This is a crippling limitation relative to first-class regex
languages like perl; postgres string translation functions are
invisible to the regex engine. I have no idea if this is fixable (I
dimly recall Tom explaining why it might not be).
merlin
From | Date | Subject | |
---|---|---|---|
Next Message | Jeff Janes | 2013-09-20 16:47:08 | Re: Partitioning V schema |
Previous Message | Manuel Kniep | 2013-09-20 15:29:11 | table inheritance and locks |