Thread: PostGreSQL and recursive queries...
_________________________________________________
Ce message et les éventuels documents joints peuvent contenir des informations confidentielles. Au cas où il ne vous serait pas destiné, nous vous remercions de bien vouloir le supprimer et en aviser immédiatement l'expéditeur. Toute utilisation de ce message non conforme à sa destination, toute diffusion ou publication, totale ou partielle et quel qu'en soit le moyen est formellement interdite. Les communications sur internet n'étant pas sécurisées, l'intégrité de ce message n'est pas assurée et la société émettrice ne peut être tenue pour responsable de son contenu. Hi,
We are using the CONNECT BY patch made by Evgen Potemkin on PostGreSQL 8.2... It works like a charm with very high performances.
But now, we are looking for the 8.3 release... Evgen Potemkin has stopped to answer about this patch (it's quite normal, he's working at mysql now...). I've tried to port the patch to the 8.3 postgresql version... It compiles but it segfault. Many data structures have changed between 8.3 and 8.2 and i'm not aware enough of postgresql internals...
So, now the solutions :
- using the connectby C function... which is min 10x slower than the patch (we may improve it a bit, but i doubt it'd beat the patch...)
- Waiting for the WITH RECURSIVE support for the 8.4 (but i don't expect anything, because this is on the todo list since many years, and i'ven't seen any code/patch since)
- Someone help me to get the patch working on the 8.3
- moving to oracle..... :-(((( or another hierarchical aware database.
It's hard to explain to our manager that if we move to the next version of postgresql there will be a performance drop.
What is the best solution
Please help me!!!
Hubert FONGARNAND
Fiducial
Hubert FONGARNAND wrote: > We are using the CONNECT BY patch made by Evgen Potemkin on > PostGreSQL 8.2... It works like a charm with very high performances. > > But now, we are looking for the 8.3 release... Evgen Potemkin has > stopped to answer about this patch (it's quite normal, he's working at > mysql now...). I've tried to port the patch to the 8.3 postgresql > version... It compiles but it segfault. Many data structures have > changed between 8.3 and 8.2 and i'm not aware enough of postgresql > internals... > > So, now the solutions : > > * using the connectby C function... which is min 10x slower > than the patch (we may improve it a bit, but i doubt it'd beat > the patch...) > * Waiting for the WITH RECURSIVE support for the 8.4 (but i > don't expect anything, because this is on the todo list since > many years, and i'ven't seen any code/patch since) > * Someone help me to get the patch working on the 8.3 > * moving to oracle..... :-(((( or another hierarchical aware > database. > > > It's hard to explain to our manager that if we move to the next version > of postgresql there will be a performance drop. > > What is the best solution > Please help me!!! > > > If you are unable to get the patch working with 8.3 yourself, you can sponsor or employ someone to do it for you, or to get WITH RECURSIVE done for 8.4, which would solve the problem forever, or maybe even both would be worth doing. cheers andrew
Le mardi 27 novembre 2007 à 10:00 -0500, Andrew Dunstan a écrit : <blockquote type="CITE"><pre> <font color="#000000">Hubert FONGARNAND wrote:</font> <font color="#000000">> We are using the CONNECT BY patch made by Evgen Potemkin on</font> <font color="#000000">> PostGreSQL 8.2... It works like a charm with very high performances.</font> <font color="#000000">></font> <font color="#000000">> But now, we are looking for the 8.3 release... Evgen Potemkin has</font> <font color="#000000">> stopped to answer about this patch (it's quite normal, he's working at</font> <font color="#000000">> mysql now...). I've tried to port the patch to the 8.3 postgresql</font> <font color="#000000">> version... It compiles but it segfault. Many data structures have</font> <font color="#000000">> changed between 8.3 and 8.2 and i'm not aware enough of postgresql</font> <font color="#000000">> internals...</font> <font color="#000000">></font> <font color="#000000">> So, now the solutions : </font> <font color="#000000">></font> <font color="#000000">> * using the connectby C function... which is min 10x slower</font> <font color="#000000">> than the patch (we may improve it a bit, but i doubt it'd beat</font> <font color="#000000">> the patch...)</font> <font color="#000000">> * Waiting for the WITH RECURSIVE support for the 8.4 (but i</font> <font color="#000000">> don't expect anything, because this is on the todo list since</font> <font color="#000000">> many years, and i'ven't seen any code/patch since)</font> <font color="#000000">> * Someone help me to get the patch working on the 8.3</font> <font color="#000000">> * moving to oracle..... :-(((( or another hierarchical aware</font> <font color="#000000">> database.</font> <font color="#000000">></font> <font color="#000000">></font> <font color="#000000">> It's hard to explain to our manager that if we move to the next version</font> <font color="#000000">> of postgresql there will be a performance drop.</font> <font color="#000000">></font> <font color="#000000">> What is the best solution</font> <font color="#000000">> Please help me!!!</font> <font color="#000000">></font> <font color="#000000">></font> <font color="#000000">> </font> <font color="#000000">If you are unable to get the patch working with 8.3 yourself, you can </font> <font color="#000000">sponsor or employ someone to do it for you,</font> </pre></blockquote><br /> I think such people is hard to find... but if someone is interested, he can contact me!<br /><br/><blockquote type="CITE"><pre> <font color="#000000"> or to get WITH RECURSIVE </font> <font color="#000000">done for 8.4, which would solve the problem forever, or maybe even both </font> <font color="#000000">would be worth doing.</font> <font color="#000000">cheers</font> <font color="#000000">andrew</font> </pre></blockquote><br /> _________________________________________________ <br /> Ce message et les éventuels documentsjoints peuvent contenir des informations confidentielles. Au cas où il ne vous serait pas destiné, nous vous remercionsde bien vouloir le supprimer et en aviser immédiatement l'expéditeur. Toute utilisation de ce message non conformeà sa destination, toute diffusion ou publication, totale ou partielle et quel qu'en soit le moyen est formellementinterdite. Les communications sur internet n'étant pas sécurisées, l'intégrité de ce message n'est pas assuréeet la société émettrice ne peut être tenue pour responsable de son contenu.