From: | Hassan <hechy_man(at)yahoo(dot)com> |
---|---|
To: | pgsql-performance(at)postgresql(dot)org |
Subject: | Re: increment Rows in an SQL Result Set postgresql |
Date: | 2006-07-15 18:53:07 |
Message-ID: | 20060715185307.5589.qmail@web30109.mail.mud.yahoo.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
Sadly I didnt write this function. It was written in C and packaged in a shared module .so. I access it thru postgresql as plpgsql function. I cannot edit the function thus.
I tried this
CREATE TEMPORARY SEQUENCE serial START 1;
SELECT nextval('serial'), astext(tmp.the_geom), street FROM shortest_path_as_geometry('bklion', 185, 10953) AS tmp LEFT JOIN (SELECT * FROM bklion) AS ss ON ss.the_geom = tmp.the_geom;
I know this is inefficient, and I surely dont know the repercussion of using the temporary sequence in a web application. Do you?
Appreciate any input.
Thanks!
- Hassan Adekoya
----- Original Message ----
From: Craig A. James <cjames(at)modgraph-usa(dot)com>
To: Hassan Adekoya <hechy_man(at)yahoo(dot)com>
Cc: pgsql-performance(at)postgresql(dot)org
Sent: Saturday, July 15, 2006 1:27:20 PM
Subject: Re: [PERFORM] increment Rows in an SQL Result Set postgresql
Hassan,
> 1. I have a function that given two parameter produces an arbitrary id, and
> text. However arbitrary the id and text are, they are in certain order. i.e. it
> is imperative that whatever processing I do, the order is preserved.
What type of function is this? Did you write it in C? An SQL procedure?
If the function is written in C, you can create a static local variable which you increment every time you call your function, and which you return along with your other two values. As long as your client is connected to the back-end server, you're guaranteed that it's a single process, and it's not multi-threaded, so this is a safe approach. However, note that if you disconnect and reconnect, your counter will be reset to zero.
If your function is written in a different language or is a procedure, you might create a sequence that your function can query.
The trick is that it is the function itself that must return the incremented value, i.e. you must return three, not two, values from your function. That way, you're not relying on any specific features of the planner, so your three values will stick together.
Craig
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Fuhr | 2006-07-15 19:02:10 | Re: Big differences in plans between 8.0 and 8.1 |
Previous Message | Hassan Adekoya | 2006-07-15 17:46:40 | increment Rows in an SQL Result Set postgresql |