| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
| Cc: | Eliot Gable <egable+pgsql-performance(at)gmail(dot)com>, Craig Ringer <craig(at)postnewspapers(dot)com(dot)au>, Craig James <craig_james(at)emolecules(dot)com>, pgsql-performance <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: Highly Efficient Custom Sorting |
| Date: | 2010-07-04 02:47:51 |
| Message-ID: | 1278211564-sup-9529@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
Excerpts from Merlin Moncure's message of sáb jul 03 18:53:46 -0400 2010:
> What about my suggestion doesn't work for your requirements? (btw,
> let me disagree with my peers and state pl/perl is lousy for this type
> of job, only sql/and pl/sql can interact with postgresql variables
> natively for the most part).
IIRC the other reason pl/perl sucks for this kind of thing is that it
forces a subtransaction to be created before the function call, which is
expensive. (I might be misremembering and what actually causes a
subtransaction is a SPI call inside a PL/Perl function, which wouldn't
apply here.)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Craig Ringer | 2010-07-04 12:38:36 | Re: Performance issues with postgresql-8.4.0 |
| Previous Message | Merlin Moncure | 2010-07-03 22:53:46 | Re: Highly Efficient Custom Sorting |