Re: [HACKERS] what can be wrong? backport plpgpsm to 8.1
Pavel Stehule [EMAIL PROTECTED] writes: I don't see any important difference, why 8.1. have to down. I dunno, but gdb is doing you no favors with such a silly backtrace. It sorta looks like you have some files built with -g and some without ... or perhaps you are trying to gdb the core file against the wrong executable? regards, tom lane ---(end of broadcast)--- TIP 1: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
Re: [HACKERS] what can be wrong? backport plpgpsm to 8.1
Pavel Stehule [EMAIL PROTECTED] writes: I don't see any important difference, why 8.1. have to down. I dunno, but gdb is doing you no favors with such a silly backtrace. It sorta looks like you have some files built with -g and some without ... or perhaps you are trying to gdb the core file against the wrong executable? propably I had to do some errors. Next cycle produce different output: #0 FreeExecutorState (estate=0x966eb2c) at execUtils.c:260 260 FreeExprContext((ExprContext *) linitial(estate-es_exprcontexts)); (gdb) bt #0 FreeExecutorState (estate=0x966eb2c) at execUtils.c:260 #1 0x00528c9c in plpgpsm_xact_cb () from /usr/local/pgsql81/lib/plpgpsm.so #2 0x080b0d81 in CallXactCallbacks (event=XACT_EVENT_COMMIT) at xact.c:2618 #3 0x080b49a8 in CommitTransaction () at xact.c:1534 #4 0x080b4c06 in CommitTransactionCommand () at xact.c:2184 #5 0x081d7c3a in finish_xact_command () at postgres.c:2021 #6 0x081d891a in exec_simple_query (query_string=0x963f844 select fx();) at postgres.c:1034 #7 0x081da153 in PostgresMain (argc=4, argv=0x95ff4b8, username=0x95ff488 root) at postgres.c:3232 #8 0x081ade68 in ServerLoop () at postmaster.c:2865 #9 0x081aed66 in PostmasterMain (argc=3, argv=0x95fd4e0) at postmaster.c:941 #10 0x0816d559 in main (argc=3, argv=0x0) at main.c:265 I hope so I see problem now. Thank you Pavel Stehule _ Citite se osamele? Poznejte nekoho vyjmecneho diky Match.com. http://www.msn.cz/ ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
Re: [HACKERS] what can be wrong? backport plpgpsm to 8.1
Pavel Stehule wrote: propably I had to do some errors. Next cycle produce different output: #0 FreeExecutorState (estate=0x966eb2c) at execUtils.c:260 260 FreeExprContext((ExprContext *) linitial(estate-es_exprcontexts)); (gdb) bt #0 FreeExecutorState (estate=0x966eb2c) at execUtils.c:260 #1 0x00528c9c in plpgpsm_xact_cb () from /usr/local/pgsql81/lib/plpgpsm.so #2 0x080b0d81 in CallXactCallbacks (event=XACT_EVENT_COMMIT) at xact.c:2618 Hmm, ISTR there were some changes to what plpgsql_xact_cb did in 8.1 ... did you check the changes to that routine? -- Alvaro Herrerahttp://www.CommandPrompt.com/ PostgreSQL Replication, Consulting, Custom Development, 24x7 support ---(end of broadcast)--- TIP 6: explain analyze is your friend
Re: [HACKERS] what can be wrong? backport plpgpsm to 8.1
Alvaro Herrera [EMAIL PROTECTED] writes: Pavel Stehule wrote: #1 0x00528c9c in plpgpsm_xact_cb () from /usr/local/pgsql81/lib/plpgpsm.so #2 0x080b0d81 in CallXactCallbacks (event=XACT_EVENT_COMMIT) at xact.c:2618 Hmm, ISTR there were some changes to what plpgsql_xact_cb did in 8.1 ... did you check the changes to that routine? Specifically I think you need to study this patch: http://archives.postgresql.org/pgsql-committers/2007-01/msg00370.php But isn't back-porting plpgpsm to old releases a waste of development and maintenance effort anyway? regards, tom lane ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
Re: [HACKERS] what can be wrong? backport plpgpsm to 8.1
Specifically I think you need to study this patch: http://archives.postgresql.org/pgsql-committers/2007-01/msg00370.php But isn't back-porting plpgpsm to old releases a waste of development and maintenance effort anyway? I unlike it and last weak I play with it. But I don't expect so Debian and RH will be support 8.3 soon. And I would to help to expansion plpgpsm. When I comment FreeExecutorState, runtime works well (with some minor problems - domains). With 8.1 support I will have much bigger group of users, testers (I hope). I have to study your patch. Thank you Pavel Stehule _ Najdete si svou lasku a nove pratele na Match.com. http://www.msn.cz/ ---(end of broadcast)--- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
