Re: [BUGS] BUG #6722: Debugger broken?
On 08.08.2012 19:05, kargor wrote: Its possible to start the debugger, but its not really easy. The control file from git has not worked, so I copied the sql file to install the functions. How did it not work? What error message did you get? Did you follow the installation instructions in the README? I copied the debugging.dll from plugins into the libdir, too, but I think this is not necessary (in the conf file the dll from plugins will be loaded). There is no reference to "debugging.dll" in the git repository, or in any old version of the debugger either IIRC, so I wonder where that came from. -- Heikki Linnakangas EnterpriseDB http://www.enterprisedb.com -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
Re: [BUGS] BUG #6722: Debugger broken?
Hi! Windows XP / Postgres 9.1.4 Of course the correct name of the dll is ..\lib\plugins\plugin_debugger.dll. My problems: * Directory ..\share\contrib is empty. * CREATE EXTENSION pldbgapi; FEHLER: konnte Erweiterungskontrolldatei »F:/progs/9.1.4/share/extension/pldbgapi.control« nicht öffnen: No such file or directory * pldbgapi--1.0.sql This file does not exist, too, nor does any similar file exist. * Then I tried the old file pldbgapi.sql from a 9.0.? server. Function name has changed, targetinfo.dll is missing. * So I have copied the pldbgapi--1.0.sql from git, updated it to use the correct dlls and then I was able to install the debugger. * For all version I have used(8.4, 9.0 and now 9.1.4) it was necessary to reboot the computer to use the debugger - restarting the database server is not enough! Greetings, Kari. Original-Nachricht > Datum: Thu, 9 Aug 2012 01:50:39 -0700 (PDT) > Von: "Heikki Linnakangas-3 [via PostgreSQL]" > > An: kargor > Betreff: Re: BUG #6722: Debugger broken? > > > On 08.08.2012 19:05, kargor wrote: > > Its possible to start the debugger, but its not really easy. > > > > The control file from git has not worked, so I copied the sql file to > > install the functions. > > How did it not work? What error message did you get? Did you follow the > installation instructions in the README? > > > I copied the debugging.dll from plugins into the libdir, too, but I > think > > this is not necessary (in the conf file the dll from plugins will be > > loaded). > > There is no reference to "debugging.dll" in the git repository, or in > any old version of the debugger either IIRC, so I wonder where that came > from. > > -- >Heikki Linnakangas >EnterpriseDB http://www.enterprisedb.com > > -- > Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-bugs > > > > > ___ > If you reply to this email, your message will be added to the discussion > below: > http://postgresql.1045698.n5.nabble.com/BUG-6722-Debugger-broken-tp5715919p5719352.html > > To unsubscribe from BUG #6722: Debugger broken?, visit > http://postgresql.1045698.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=5715919&code=a2FybGdvcnRvbkBnbXguYXR8NTcxNTkxOXwxNzgyNjM3ODYy -- - Karl Gorton karlgor...@gmx.at -- View this message in context: http://postgresql.1045698.n5.nabble.com/BUG-6722-Debugger-broken-tp5715919p5719372.html Sent from the PostgreSQL - bugs mailing list archive at Nabble.com.
Re: [BUGS] BUG #6722: Debugger broken?
On 09.08.2012 15:07, kargor wrote: * CREATE EXTENSION pldbgapi; FEHLER: konnte Erweiterungskontrolldatei »F:/progs/9.1.4/share/extension/pldbgapi.control« nicht öffnen: No such file or directory Did you use MinGW or MSVC to build it? Did you perform the install step, ie. "make install" ? -- Heikki Linnakangas EnterpriseDB http://www.enterprisedb.com -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
Re: [BUGS] BUG #7478: Error when using pg_restore
From: pgsql-bugs-ow...@postgresql.org [mailto:pgsql-bugs-ow...@postgresql.org] On Behalf Of jefersonbl...@gmail.com Sent: Friday, August 03, 2012 4:07 PM > The following bug has been logged on the website: > Bug reference: 7478 > Logged by: jeferson > Email address: jefersonbl...@gmail.com > PostgreSQL version: 9.1.4 > Operating system: Windows 7 > Description: > pg_dump -Fc -U usuario -d banco -f d:\arquivo.backup > However the restourar pg_restore with tables that are large give the error: > [compres_io] invalid block type, already checked on some other forums people > have had the same problem when using and enjoying the dump format with > custom, I tried restourar the contents into a file. sql but when you get 14 > gigs of the entity for it. Could you provide the exact error message and any logs related to this? Have you tried it with less data? With Regards, Amit Kapila. -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
Re: [BUGS] BUG #6722: Debugger broken?
I use the binaries provided on the download page. I have not compiled anything - I'm a 'stupid' windows user... Original-Nachricht > Datum: Thu, 9 Aug 2012 05:21:27 -0700 (PDT) > Von: "Heikki Linnakangas-3 [via PostgreSQL]" > > An: kargor > Betreff: Re: BUG #6722: Debugger broken? > > > On 09.08.2012 15:07, kargor wrote: > > * CREATE EXTENSION pldbgapi; > > FEHLER: konnte Erweiterungskontrolldatei > »F:/progs/9.1.4/share/extension/pldbgapi.control« nicht öffnen: No such file > or directory > > Did you use MinGW or MSVC to build it? Did you perform the install step, > ie. "make install" ? > > -- >Heikki Linnakangas >EnterpriseDB http://www.enterprisedb.com > > -- > Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-bugs > > > > > ___ > If you reply to this email, your message will be added to the discussion > below: > http://postgresql.1045698.n5.nabble.com/BUG-6722-Debugger-broken-tp5715919p5719373.html > > To unsubscribe from BUG #6722: Debugger broken?, visit > http://postgresql.1045698.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=5715919&code=a2FybGdvcnRvbkBnbXguYXR8NTcxNTkxOXwxNzgyNjM3ODYy -- - Karl Gorton karlgor...@gmx.at -- View this message in context: http://postgresql.1045698.n5.nabble.com/BUG-6722-Debugger-broken-tp5715919p5719389.html Sent from the PostgreSQL - bugs mailing list archive at Nabble.com.
Re: [BUGS] BUG #7478: Error when using pg_restore
Sure, no problem. But I also might take some time to do further analysis as I am little busy with other things as well. Hope it will not impact you much. With Regards, Amit Kapila. From: Jeferson Braga [mailto:jefersonbl...@gmail.com] Sent: Thursday, August 09, 2012 7:42 PM To: Amit Kapila Cc: pgsql-bugs@postgresql.org Subject: Re: [BUGS] BUG #7478: Error when using pg_restore Good morning, Can I send you when I get home I send you the log. and a print error. Thank you for your attention. 2012/8/9 Amit Kapila From: pgsql-bugs-ow...@postgresql.org [mailto:pgsql-bugs-ow...@postgresql.org] On Behalf Of jefersonbl...@gmail.com Sent: Friday, August 03, 2012 4:07 PM > The following bug has been logged on the website: > Bug reference: 7478 > Logged by: jeferson > Email address: jefersonbl...@gmail.com > PostgreSQL version: 9.1.4 > Operating system: Windows 7 > Description: > pg_dump -Fc -U usuario -d banco -f d:\arquivo.backup > However the restourar pg_restore with tables that are large give the error: > [compres_io] invalid block type, already checked on some other forums people > have had the same problem when using and enjoying the dump format with > custom, I tried restourar the contents into a file. sql but when you get 14 > gigs of the entity for it. Could you provide the exact error message and any logs related to this? Have you tried it with less data? With Regards, Amit Kapila. -- Jeferson Braga do Carmo Analista / Desenvolvedor .Net 61 8237-1888 61 3359-3781
Re: [BUGS] BUG #6722: Debugger broken?
On 09.08.2012 17:07, kargor wrote: I use the binaries provided on the download page. I have not compiled anything - I'm a 'stupid' windows user... Ok, I see. I just downloaded the 9.1.4 installer, and you're right, there is no pldbgapi.control file anywhere. Looking at the README.pldebugger file, the version of pldebugger that the installer includes certainly should include that file. Dave, is this a packaging issue? Which version of pldebugger was included in the 9.1.4 installers? -- Heikki Linnakangas EnterpriseDB http://www.enterprisedb.com -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
Re: [BUGS] BUG #6722: Debugger broken?
On Thu, Aug 9, 2012 at 3:51 PM, Heikki Linnakangas wrote: > On 09.08.2012 17:07, kargor wrote: >> >> I use the binaries provided on the download page. I have not compiled >> anything - I'm a 'stupid' windows user... > > > Ok, I see. I just downloaded the 9.1.4 installer, and you're right, there is > no pldbgapi.control file anywhere. Looking at the README.pldebugger file, > the version of pldebugger that the installer includes certainly should > include that file. > > Dave, is this a packaging issue? Which version of pldebugger was included in > the 9.1.4 installers? It uses the head of the PRE_9_2 branch. -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
Re: [BUGS] BUG #7478: Error when using pg_restore
Good morning, Can I send you when I get home I send you the log. and a print error. Thank you for your attention. 2012/8/9 Amit Kapila > From: pgsql-bugs-ow...@postgresql.org [mailto: > pgsql-bugs-ow...@postgresql.org] On Behalf Of jefersonbl...@gmail.com > Sent: Friday, August 03, 2012 4:07 PM > > > The following bug has been logged on the website: > > > Bug reference: 7478 > > Logged by: jeferson > > Email address: jefersonbl...@gmail.com > > PostgreSQL version: 9.1.4 > > Operating system: Windows 7 > > Description: > > > pg_dump -Fc -U usuario -d banco -f d:\arquivo.backup > > > However the restourar pg_restore with tables that are large give the > error: > > [compres_io] invalid block type, already checked on some other forums > people > > have had the same problem when using and enjoying the dump format with > > custom, I tried restourar the contents into a file. sql but when you get > 14 > > gigs of the entity for it. > > Could you provide the exact error message and any logs related to this? > Have you tried it with less data? > > With Regards, > Amit Kapila. > > -- *Jeferson Braga do Carmo* *Analista / Desenvolvedor .Net* 61 8237-1888 61 3359-3781
Re: [BUGS] server crash with "process 22821 releasing ProcSignal slot 32, but it contains 0"
On Tue, Jun 26, 2012 at 12:09 PM, Merlin Moncure wrote: > On Tue, Jun 26, 2012 at 12:02 PM, Tom Lane wrote: >> Merlin Moncure writes: >>> I suspect (but haven't had time to prove and may not for several days >>> -- unfortunately going on vacation momentarily) that this might be >>> caused by pl/sh. >> >> Hm. The reported symptoms might be explainable if something had caused >> multiple threads to become active within the backend process --- then >> it would be plausible for it to try to do proc_exit cleanup twice. >> Which would explain the first two errors, though I'm not sure how that >> leads to failing to disown the process latch, as the third error >> suggests must have happened. But I don't know enough about pl/sh to >> know if it could cause threading activation. >> >>> In particular, we have a routine that was >>> inadvertently applied to the database in with windows cr/lf instead of >>> the normal linux newline. >> >> This doesn't seem real promising as an explanation ... > > right -- just a suspicion. maybe the relevant point was that it > immediately failed. operator invoking the busted routine (which I had > to fix) and the crash were highly correlated, although it does not > always crash. yesterday was very heavy load and today not so much. Follow up on this. It is pl/sh and it is a newline issue: one of the developers is using a tool (I think pgadmin?) that is sticking \r characters at the end of every line which is throwing off pl/sh's shebang parsing. The issuing query gets an error along the lines of 'could not exec' and the server goes belly up if there is significant concurrent load when that's issued. This is an out of date pl/sh, so I'm going to upgrade it and try and reproduce. If I still can, I'll supply a test case. merlin -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
