Re: Highly Efficient Custom Sorting

From: Alvaro Herrera
Subject: Re: Highly Efficient Custom Sorting
Date: ,
Msg-id: 1278211564-sup-9529@alvh.no-ip.org
(view: Whole thread, Raw)
In response to: Re: Highly Efficient Custom Sorting  (Merlin Moncure)
List: pgsql-performance

Tree view

Highly Efficient Custom Sorting  (Eliot Gable, )
 Re: Highly Efficient Custom Sorting  (Craig Ringer, )
  Re: Highly Efficient Custom Sorting  (Tom Lane, )
   Re: Highly Efficient Custom Sorting  (Eliot Gable, )
    Re: Highly Efficient Custom Sorting  (Matthew Wakeling, )
     Re: Highly Efficient Custom Sorting  (Merlin Moncure, )
    Re: Highly Efficient Custom Sorting  (Craig James, )
     Re: Highly Efficient Custom Sorting  (Craig Ringer, )
      Re: Highly Efficient Custom Sorting  (Eliot Gable, )
       Re: Highly Efficient Custom Sorting  (Merlin Moncure, )
        Re: Highly Efficient Custom Sorting  (Eliot Gable, )
         Re: Highly Efficient Custom Sorting  (Merlin Moncure, )
          Re: Highly Efficient Custom Sorting  (Alvaro Herrera, )
         Re: Highly Efficient Custom Sorting  (Robert Haas, )
          Re: Highly Efficient Custom Sorting  (Eliot Gable, )
           Re: Highly Efficient Custom Sorting  (Joe Conway, )
            Re: Highly Efficient Custom Sorting  (Eliot Gable, )
             Re: Highly Efficient Custom Sorting  (Eliot Gable, )
              Re: Highly Efficient Custom Sorting  (Tom Lane, )
               Re: Highly Efficient Custom Sorting  (Eliot Gable, )
                Re: Highly Efficient Custom Sorting  (Kenneth Marshall, )
 Re: Highly Efficient Custom Sorting  (Merlin Moncure, )

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.)


pgsql-performance by date:

From: Alvaro Herrera
Date:
Subject: Re: Highly Efficient Custom Sorting
From: "Sachin Kumar"
Date:
Subject: Performance issues with postgresql-8.4.0