[BUGS] BUG #6722: Debugger broken?
The following bug has been logged on the website: Bug reference: 6722 Logged by: Jan-Peter Seifert Email address: jan-peter.seif...@gmx.de PostgreSQL version: 9.1.4 Operating system: Windows 7 Enterprise (64-bit) Description: Hello, it seems that the debugger doesn't work with current minor versions of PostgreSQL. I don't even get the debugging option shown here: http://stackoverflow.com/questions/7865615/debug-postgresql-function-using-pgadmin It could be connected to these changes: http://git.postgresql.org/gitweb/?p=pldebugger.git;a=log I activated the debugger in postgresql.conf and restarted the server(s)): shared_preload_libraries = '$libdir/plugins/plugin_debugger.dll' As there only exists the contrib-script I tried to execute this: c:\Program Files\PostgreSQL\9.1\share\contrib\pldbgapi.sql I only get a function not found ( in debugger.dll ) error: FEHLER: konnte Funktion »plpgsql_oid_debug« nicht in Datei »C:/Program Files/PostgreSQL/9.1/lib/plugins/plugin_debugger.dll« finden SQL Status:42883 If I switch to this it works: CREATE OR REPLACE FUNCTION pldbg_oid_debug( OID ) RETURNS INTEGER AS '$libdir/plugins/plugin_debugger' LANGUAGE C STRICT; It's the same with 8.4.12 ( 32-bit ) and 9.0.8 ( 64-bit ). It's the very same install script for each version. In 8.4.12 I also have these two files: c:\Program Files (x86)\PostgreSQL\8.4\share\contrib\pldbgapi--1.0.sql and c:\Program Files (x86)\PostgreSQL\8.4\share\contrib\pldbgapi--unpackaged--1.0.sql Obviously they are for PostgreSQL 9.1. The first says install with 'CREATE EXTENSION pldbgapi' There's no such extension - neither in Windows nor Ubuntu ( One click installer and aptitude ) nor in the docs. With best regards, Peter -- 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 On Mon, Jul 9, 2012 at 12:58 PM, jan-peter.seif...@gmx.de wrote: The following bug has been logged on the website: Bug reference: 6722 Logged by: Jan-Peter Seifert Email address: jan-peter.seif...@gmx.de PostgreSQL version: 9.1.4 Operating system: Windows 7 Enterprise (64-bit) Description: Hello, it seems that the debugger doesn't work with current minor versions of PostgreSQL. I don't even get the debugging option shown here: http://stackoverflow.com/questions/7865615/debug-postgresql-function-using-pgadmin It could be connected to these changes: http://git.postgresql.org/gitweb/?p=pldebugger.git;a=log I activated the debugger in postgresql.conf and restarted the server(s)): shared_preload_libraries = '$libdir/plugins/plugin_debugger.dll' As there only exists the contrib-script I tried to execute this: c:\Program Files\PostgreSQL\9.1\share\contrib\pldbgapi.sql I only get a function not found ( in debugger.dll ) error: FEHLER: konnte Funktion »plpgsql_oid_debug« nicht in Datei »C:/Program Files/PostgreSQL/9.1/lib/plugins/plugin_debugger.dll« finden SQL Status:42883 If I switch to this it works: CREATE OR REPLACE FUNCTION pldbg_oid_debug( OID ) RETURNS INTEGER AS '$libdir/plugins/plugin_debugger' LANGUAGE C STRICT; It's the same with 8.4.12 ( 32-bit ) and 9.0.8 ( 64-bit ). It's the very same install script for each version. In 8.4.12 I also have these two files: c:\Program Files (x86)\PostgreSQL\8.4\share\contrib\pldbgapi--1.0.sql and c:\Program Files (x86)\PostgreSQL\8.4\share\contrib\pldbgapi--unpackaged--1.0.sql Obviously they are for PostgreSQL 9.1. The first says install with 'CREATE EXTENSION pldbgapi' There's no such extension - neither in Windows nor Ubuntu ( One click installer and aptitude ) nor in the docs. It looks like it got broken as a result of this commit: http://git.postgresql.org/gitweb/?p=pldebugger.git;a=commit;h=54d993c04809da7cda79013a55b679a615c7dce1 Dharmendra; can you please take a look at this? A quick look at my 9.1 installation shows that the control file is missing along with the SQL scripts. I only have the old pre-extension SQL script from the previous point release (that should really be deleted). For 8.4/9.0 of course, the old installation technique should be used. Please also ensure the docs are appropriate for all branches. Thanks. -- 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
[BUGS] BUG #6725: hot-standby slave repeatable crashed after restart (GIN error)
The following bug has been logged on the website: Bug reference: 6725 Logged by: Maxim Boguk Email address: maxim.bo...@gmail.com PostgreSQL version: 9.0.7 Operating system: Debian Linux Description: Hi, On one of my production databases hot-standby server start repeatable crash after restart. There is log: 2012-07-10 03:30:20 MSK 12034 postgres@postgres from [local] [vxid:2/0 txid:0] [CHECKPOINT] LOG: duration: 100.262 ms statement: checkpoint; 2012-07-10 03:30:24 MSK 12034 postgres@postgres from [local] [vxid:2/0 txid:0] [CHECKPOINT] LOG: duration: 100.207 ms statement: checkpoint; 2012-07-10 03:30:41 MSK 24618 @ from [vxid: txid:0] [] LOG: received fast shutdown request 2012-07-10 03:30:41 MSK 24618 @ from [vxid: txid:0] [] LOG: aborting any active transactions 2012-07-10 03:30:41 MSK 25312 @ from [vxid: txid:0] [] FATAL: terminating walreceiver process due to administrator command 2012-07-10 03:30:41 MSK 24646 @ from [vxid: txid:0] [] LOG: shutting down 2012-07-10 03:30:41 MSK 24646 @ from [vxid: txid:0] [] LOG: database system is shut down 2012-07-10 03:30:45 MSK 12202 @ from [vxid: txid:0] [] LOG: database system was shut down in recovery at 2012-07-10 03:30:41 MSK 2012-07-10 03:30:45 MSK 12202 @ from [vxid: txid:0] [] LOG: entering standby mode 2012-07-10 03:30:45 MSK 12202 @ from [vxid:1/0 txid:0] [] LOG: redo starts at 127C/51EF6798 2012-07-10 03:31:35 MSK 12202 @ from [vxid:1/0 txid:0] [] PANIC: GIN metapage disappeared 2012-07-10 03:31:35 MSK 12202 @ from [vxid:1/0 txid:0] [] CONTEXT: xlog redo Update metapage, node: 1663/62450/27663577 blkno: 2164 2012-07-10 03:31:35 MSK 12189 @ from [vxid: txid:0] [] LOG: startup process (PID 12202) was terminated by signal 6: Aborted 2012-07-10 03:31:35 MSK 12189 @ from [vxid: txid:0] [] LOG: terminating any other active server processes 2012-07-10 03:33:37 MSK 13071 @ from [vxid: txid:0] [] LOG: database system was interrupted while in recovery at log time 2012-07-10 02:17:21 MSK 2012-07-10 03:33:37 MSK 13071 @ from [vxid: txid:0] [] HINT: If this has occurred more than once some data might be corrupted and you might need to choose an earlier recovery target. 2012-07-10 03:33:37 MSK 13071 @ from [vxid: txid:0] [] LOG: entering standby mode 2012-07-10 03:33:37 MSK 13071 @ from [vxid:1/0 txid:0] [] LOG: redo starts at 127C/51EF6798 2012-07-10 03:34:15 MSK 13071 @ from [vxid:1/0 txid:0] [] PANIC: GIN metapage disappeared 2012-07-10 03:34:15 MSK 13071 @ from [vxid:1/0 txid:0] [] CONTEXT: xlog redo Update metapage, node: 1663/62450/27663577 blkno: 2164 2012-07-10 03:34:15 MSK 13065 @ from [vxid: txid:0] [] LOG: startup process (PID 13071) was terminated by signal 6: Aborted 2012-07-10 03:34:15 MSK 13065 @ from [vxid: txid:0] [] LOG: terminating any other active server processes and so on. I almost sure there are no disk corruption or such errors. Now some additional information from the master server: 1)1663/62450/27663577 - corresponding to the pg_default tablespace and wsfilm database. However, no entries with relfilenode=27663577 were found in pg_class. In the same time: ls -la ./9.0/main/base/62450/27663577 -rw--- 1 postgres postgres 0 Июл 10 02:29 ./9.0/main/base/62450/27663577 In wsfilm db only one GIN index exists: wsfilm=# SELECT * from pg_indexes where indexdef like '%gin%'; -[ RECORD 1 ]--- schemaname | public tablename | movie indexname | movie_fti_idx tablespace | indexdef | CREATE INDEX movie_fti_idx ON movie USING gin (fti) But it has different relfilenode: wsfilm=# SELECT relfilenode from pg_class where relname='movie_fti_idx'; -[ RECORD 1 ]- relfilenode | 27677714 2)Just few minutes before that index was rebuild on the master database: 2012-07-10 02:29:50 MSK 1480 postgres@wsfilm from [local] [vxid:33/3324338 txid:0] [idle] LOG: statement: CREATE INDEX CONCURRENTLY pgcompactor_tmp1436 ON movie USING gin (fti); 2012-07-10 02:29:52 MSK 1480 postgres@wsfilm from [local] [vxid:33/3324343 txid:0] [idle] LOG: statement: BEGIN; DROP INDEX public.movie_fti_idx; ALTER INDEX public.pgcompactor_tmp1436 RENAME TO movie_fti_idx; END; My theory that the wal replay trying replay GIN index information on already dropped index. -- 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 #6725: hot-standby slave repeatable crashed after restart (GIN error)
maxim.bo...@gmail.com writes: On one of my production databases hot-standby server start repeatable crash after restart. 2012-07-10 03:31:35 MSK 12202 @ from [vxid:1/0 txid:0] [] PANIC: GIN metapage disappeared This is fixed in current minor releases. http://git.postgresql.org/gitweb/?p=postgresql.gita=commitdiffh=268ca4f57ea2dc3bf0dfb0f5c17fbda269b5d462 regards, tom lane -- 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 #6725: hot-standby slave repeatable crashed after restart (GIN error)
2012-07-10 03:31:35 MSK 12202 @ from [vxid:1/0 txid:0] [] PANIC: GIN metapage disappeared This is fixed in current minor releases. http://git.postgresql.org/gitweb/?p=postgresql.gita=commitdiffh=268ca4f57ea2dc3bf0dfb0f5c17fbda269b5d462 regards, tom lane Ooops sorry, I should check a release notes from the atest version before posting new bugs. Thank you. Kind Regards, Maksym
Re: [BUGS] BUG #6724: EXCEPTION syntax not recgonised
Hello This is not bug keyword EXCEPTION is supported only in plpgsql. Regards Pavel Stehule 2012/7/9 chine.b...@yahoo.com: The following bug has been logged on the website: Bug reference: 6724 Logged by: Chine Bleu Email address: chine.b...@yahoo.com PostgreSQL version: 9.0.4 Operating system: macosx Description: query: BEGIN INSERT INTO config (name, value) VALUES (E'dbexp', E'10'); EXCEPTION WHEN unique_violation THEN UPDATE config SET value=E'10' WHERE name=E'dbexp'; END error: fatal query: ERROR: syntax error at or near INSERT LINE 2: INSERT INTO config (name, value) VALUES (E'dbexp', E'10'); ^ query: BEGIN; INSERT INTO config (name, value) VALUES (E'dbexp', E'10'); EXCEPTION WHEN unique_violation THEN UPDATE config SET value=E'10' WHERE name=E'dbexp'; END error: fatal query: ERROR: syntax error at or near EXCEPTION LINE 3: EXCEPTION WHEN unique_violation THEN ^ This is so much easier than implementing that horror of REPLACE everyone else has somehow figured out how to implement. And, no, I don't really expect an answer. I will continue to use the DELETE...;;INSERT... improvement on REPLACE. -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
