Re: [BUGS] BUG #3953: No PostGIS option in installer
Thanks for the clarification, Dave. I posted the question here because this was the only place I could find where there already seemed to be a relevant discussion, but now I know about the EDB forum that's obviously a much better place. In terms of the problem, I downloaded the EDB AS 8.3 installer (not MSI - you're right of course) from your website yesterday and went through the installation process several times, trying various combinations of options or accepting all the default options. PostGIS simply did not install and I couldn't even find it in the folders. Obviously there's something fishy going on there, but maybe it's something to do with my setup, although given the simplicity of the installer it would seem that there are only a limited number of places where I could screw it up! In the meantime, I've gone back to EDB AS 8.2, which clearly gives you the option of installing PostGIS during the installation process. Works for me, anyway. To be honest, I think the idea of having the option to install various components, including PostGIS, as in 8.2, makes for a better and more flexible installer. You can still go for the defaults if required, but at least you have a little more room to tailor your installation and investigate any problems. Maybe your other users might appreciate this flexibility? Thanks again for your help. -- View this message in context: http://www.nabble.com/BUG--3953%3A-No-PostGIS-option-in-installer-tp15428856p16656751.html Sent from the PostgreSQL - bugs mailing list archive at Nabble.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 #4106: WHERE - clause in view works only sometimes
Hello Tom, it seems that i can't reproduce it too at the moment. When i see the bug again i will directly send you the data, but it must be something like that: INSERT INTO benutzer (pnr, vorname, nachname, nutzerkennung, passwort, plz, ort, strasse, hausnummer, telefon_dienst, telefon_privat, email, anzahl_tage_erinnerung, gebietsschutz) VALUES (100, 'Alexander', 'Strotmann', 'alex', '534b44a19bf18d20b71ecc4eb77c572f', '1', 'Test', 'Teststraße', '7', '+49 0251/123', NULL, '[EMAIL PROTECTED]', 30, false); INSERT INTO benutzer (pnr, vorname, nachname, nutzerkennung, passwort, plz, ort, strasse, hausnummer, telefon_dienst, telefon_privat, email, anzahl_tage_erinnerung, gebietsschutz) VALUES (101, 'Stephan', 'Künster', 'stephan', 'bf1f92de980819a99356289142b9590d', '2', 'Test', 'Test-Weg', '444', '0251 123', NULL, '[EMAIL PROTECTED]', 40, false); INSERT INTO rollenhistorie (pnr, rolle, seit, bis) VALUES (101, 'admin', '2008-03-27 17:35:34.953', '2008-04-11 16:53:14.657134'); INSERT INTO rollenhistorie (pnr, rolle, seit, bis) VALUES (100, 'admin', '2008-04-12 14:13:57.215625', '2008-04-13 10:32:42.535246'); INSERT INTO rollenhistorie (pnr, rolle, seit, bis) VALUES (100, 'vorg', '2008-04-13 10:32:42.535246', '2008-04-13 10:32:48.113442'); INSERT INTO rollenhistorie (pnr, rolle, seit, bis) VALUES (100, 'admin', '2008-04-13 10:32:48.113442', '2008-04-13 10:33:14.770033'); INSERT INTO rollenhistorie (pnr, rolle, seit, bis) VALUES (101, 'vorg', '2008-04-11 16:53:14.657134', '2008-04-11 17:21:30.642962'); INSERT INTO rollenhistorie (pnr, rolle, seit, bis) VALUES (100, 'vorg', '2008-04-13 10:33:14.770033', '2008-04-13 10:40:27.713075'); INSERT INTO rollenhistorie (pnr, rolle, seit, bis) VALUES (100, 'admin', '2008-04-13 10:40:27.713075', NULL); INSERT INTO rollenhistorie (pnr, rolle, seit, bis) VALUES (101, 'admin', '2008-04-11 17:21:30.642962', '2008-04-11 18:09:59.498309'); INSERT INTO rollenhistorie (pnr, rolle, seit, bis) VALUES (101, 'admin', '2008-04-11 18:12:03.656148', '2008-04-13 10:40:48.947722'); INSERT INTO rollenhistorie (pnr, rolle, seit, bis) VALUES (101, 'tl', '2008-04-13 10:40:48.947722', '2008-04-13 10:41:44.417182'); INSERT INTO rollenhistorie (pnr, rolle, seit, bis) VALUES (101, 'vorg', '2008-04-11 18:09:59.498309', '2008-04-11 18:12:03.656148'); INSERT INTO rollenhistorie (pnr, rolle, seit, bis) VALUES (101, 'vorg', '2008-04-13 10:41:44.417182', '2008-04-13 10:49:02.454039'); INSERT INTO rollenhistorie (pnr, rolle, seit, bis) VALUES (101, 'admin', '2008-04-13 10:49:02.454039', '2008-04-13 11:00:57.23847'); INSERT INTO rollenhistorie (pnr, rolle, seit, bis) VALUES (101, 'tl', '2008-04-13 11:00:57.23847', '2008-04-13 11:02:44.646095'); INSERT INTO rollenhistorie (pnr, rolle, seit, bis) VALUES (101, 'admin', '2008-04-13 11:02:44.646095', NULL); Tom Lane schrieb: Alexander Strotmann <[EMAIL PROTECTED]> writes: Ok, sorry, here it is all: [ Please keep the mailing list cc'd ] I couldn't reproduce a problem with these table definitions and some simple dummy data. Can you see any pattern to when it fails for you and when it doesn't? What plan do you get from EXPLAIN SELECT * FROM benutzer_mit_rolle_vw ? "Hash Join (cost=1.35..18.60 rows=11 width=307)" " Hash Cond: (benutzer.pnr = rollenhistorie.pnr)" " -> Seq Scan on benutzer (cost=0.00..14.60 rows=226 width=284)" "Filter: (((nutzerkennung)::text <> 'system'::text) AND ((nutzerkennung)::text <> 'marketingpool'::text) AND ((nutzerkennung)::text <> 'deleted'::text) AND ((nutzerkennung)::text !~~ 'dummy_%'::text))" " -> Hash (cost=1.21..1.21 rows=11 width=27)" "-> Seq Scan on rollenhistorie (cost=0.00..1.21 rows=11 width=27)" " Filter: (bis IS NULL)" What non-default postgresql.conf settings are you using? I never changed something in postgresql.conf. So it should be everything default. Regards, Alex Strotmann regards, tom lane Postgre version: PostgreSQL version 8.2.5 we have this table: CREATE TABLE rollenhistorie ( pnr integer NOT NULL, rolle character varying NOT NULL, seit timestamp without time zone NOT NULL, bis timestamp without time zone, CONSTRAINT rollenhistorie_pkey PRIMARY KEY (pnr, seit) ) WITHOUT OIDS; and this table: CREATE TABLE benutzer ( pnr serial NOT NULL, vorname character varying(30) NOT NULL, nachname character varying(30) NOT NULL, nutzerkennung character varying(20) NOT NULL, passwort character varying(32) NOT NULL, plz character varying(10) NOT NULL, ort character varying(30) NOT NULL, strasse character varying(30) NOT NULL, hausnummer character varying(5) NOT NULL, telefon_dienst character varying(20) NOT NULL, email character varying(40) NOT NULL, anzahl_tage_erinnerung integer NOT NULL DEFAULT 30, gebietsschutz boolean NOT NULL DEFAULT false, CONSTRAINT benutzer_pkey PRIMARY KEY (pnr), CONSTRAINT
Re: [BUGS] BUG #3983: pgxs files still missing in win32 install (8.3.1)
Magnus Hagander wrote: In general, mingw built modules should load just fine in msvc built postgres. AFAIK, that's how PostGIS does it for 8.3 (though I know Mark is working on getting MSVC build support for them). Debugging may be a bit harder (since they use different kinds of debug symbols - postgres uses Windows style and mingw uses mingw style), but it should certainly load. What trouble exactly are you seeing? Basically, "Procedure not found", even though it is there. Also note that the same R.dll is being used from the MinGW Postgres installation (where plr loads successfully) and the MSVC Postgres. Joe p.s. actual output below 8<-- Welcome to psql 8.3.1, the PostgreSQL interactive terminal. Type: \copyright for distribution terms \h for help with SQL commands \? for help with psql commands \g or terminate with semicolon to execute query \q to quit Warning: Console code page (437) differs from Windows code page (1252) 8-bit characters might not work correctly. See psql reference page "Notes for Windows users" for details. postgres=# load '$libdir/dblink'; LOAD postgres=# load '$libdir/plr'; ERROR: could not load library "C:/Program Files/PostgreSQL/8.3/lib/plr.dll": The specified procedure could not be found. postgres=# CREATE TYPE plr_environ_type AS (name text, value text); CREATE TYPE postgres=# CREATE OR REPLACE FUNCTION plr_environ () postgres-# RETURNS SETOF plr_environ_type postgres-# AS '$libdir/plr','plr_environ' postgres-# LANGUAGE 'C'; ERROR: could not load library "C:/Program Files/PostgreSQL/8.3/lib/plr.dll": The specified procedure could not be found. Microsoft Windows XP [Version 5.1.2600] (C) Copyright 1985-2001 Microsoft Corp. C:\Documents and Settings\jconway>dir "C:\Program Files\PostgreSQL\8.3\lib" Volume in drive C has no label. Volume Serial Number is A006-8372 Directory of C:\Program Files\PostgreSQL\8.3\lib [...] 03/17/2008 03:49 AM57,344 dblink.dll [...] 03/17/2008 03:47 AM28,264 libpq.lib [...] 04/06/2008 12:50 PM 686,579 plr.dll -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
[BUGS] tracking down a crash bug
Hello. I need help tracking down a crash bug. I'm running 8.2.7 I've had my database go into recovery mode three times so far today under user load. /etc/init.d/postgresql-8.2 stop would stop the backend but leave a few processes behind like this postgres 22318 0.0 0.0 45724 1272 ?Ss Apr11 0:13 postgres: app1101 app1101 10.255.7.159(44567) idle postgres 24365 0.0 0.0 45724 1224 ?Ss Apr11 0:02 postgres: app2280 app2280 10.255.7.159(51010) idle postgres 5649 0.0 0.0 45368 1180 ?Ss Apr11 0:00 postgres: app9452 app9452 10.255.7.159(43141) idle I would then have to kill -9 these process. Looking at the postgres log I find only this... 2008-04-13 12:20:10 PDT STATEMENT: SELECT version FROM schema_info 2008-04-13 12:21:14 PDT ERROR: relation "schema_info" does not exist 2008-04-13 12:21:14 PDT STATEMENT: SELECT version FROM schema_info 2008-04-13 12:26:48 PDT LOG: background writer process (PID 965) was terminated by signal 9 2008-04-13 12:26:48 PDT LOG: terminating any other active server processes 2008-04-13 12:26:48 PDT WARNING: terminating connection because of crash of another server process 2008-04-13 12:26:48 PDT DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory. 2008-04-13 12:26:48 PDT HINT: In a moment you should be able to reconnect to the database and repeat your command. [ repeat several hundred times ] 2008-04-13 12:28:11 PDT FATAL: the database system is in recovery mode [ repeat several hundred times ] 2008-04-13 12:33:00 PDT LOG: incomplete startup packet 2008-04-13 12:33:00 PDT LOG: received fast shutdown request 2008-04-13 12:33:12 PDT FATAL: the database system is shutting down [ repeat a dozen times ] 2008-04-13 12:34:00 PDT LOG: received immediate shutdown request 2008-04-13 12:34:02 PDT LOG: could not load root certificate file "root.crt": No such file or directory 2008-04-13 12:34:02 PDT DETAIL: Will not verify client certificates. 2008-04-13 12:34:20 PDT LOG: could not create IPv6 socket: Address family not supported by protocol 2008-04-13 12:34:20 PDT LOG: could not resolve "localhost": Name or service not known 2008-04-13 12:34:20 PDT LOG: disabling statistics collector for lack of working socket 2008-04-13 12:34:20 PDT WARNING: autovacuum not started because of misconfiguration 2008-04-13 12:34:20 PDT HINT: Enable options "stats_start_collector" and "stats_row_level". 2008-04-13 12:34:20 PDT LOG: database system was interrupted at 2008-04-13 12:22:44 PDT 2008-04-13 12:34:20 PDT LOG: checkpoint record is at 0/594FDF58 2008-04-13 12:34:20 PDT LOG: redo record is at 0/5946B830; undo record is at 0/0; shutdown FALSE 2008-04-13 12:34:20 PDT LOG: next transaction ID: 0/2979312; next OID: 106497 2008-04-13 12:34:20 PDT LOG: next MultiXactId: 1; next MultiXactOffset: 0 2008-04-13 12:34:20 PDT LOG: database system was not properly shut down; automatic recovery in progress 2008-04-13 12:34:20 PDT LOG: redo starts at 0/5946B830 2008-04-13 12:34:21 PDT LOG: incomplete startup packet 2008-04-13 12:34:21 PDT LOG: record with zero length at 0/5957A3EC 2008-04-13 12:34:21 PDT LOG: redo done at 0/5957A3C4 2008-04-13 12:34:21 PDT LOG: database system is ready Any advice on how I can get this bug identified and squashed? I suspect it's in the create/drop [database,role,schema]. I've used postgres for 7 years without issues at this point. The only thing different now are my usage patterns. Since I'm offering a database as a service to my users I'm adding and dropping databases roles and schemas constantly. Thanks
[BUGS] tracking down a crash bug
Hello. I need help tracking down a crash bug. I'm running 8.2.7 I've had my database go into recovery mode three times so far today under user load. /etc/init.d/postgresql-8.2 stop would stop the backend but leave a few processes behind like this postgres 22318 0.0 0.0 45724 1272 ?Ss Apr11 0:13 postgres: app1101 app1101 10.255.7.159(44567) idle postgres 24365 0.0 0.0 45724 1224 ?Ss Apr11 0:02 postgres: app2280 app2280 10.255.7.159(51010) idle postgres 5649 0.0 0.0 45368 1180 ?Ss Apr11 0:00 postgres: app9452 app9452 10.255.7.159(43141) idle I would then have to kill -9 these process. Looking at the postgres log I find only this... 2008-04-13 12:20:10 PDT STATEMENT: SELECT version FROM schema_info 2008-04-13 12:21:14 PDT ERROR: relation "schema_info" does not exist 2008-04-13 12:21:14 PDT STATEMENT: SELECT version FROM schema_info 2008-04-13 12:26:48 PDT LOG: background writer process (PID 965) was terminated by signal 9 2008-04-13 12:26:48 PDT LOG: terminating any other active server processes 2008-04-13 12:26:48 PDT WARNING: terminating connection because of crash of another server process 2008-04-13 12:26:48 PDT DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory. 2008-04-13 12:26:48 PDT HINT: In a moment you should be able to reconnect to the database and repeat your command. [ repeat several hundred times ] 2008-04-13 12:28:11 PDT FATAL: the database system is in recovery mode [ repeat several hundred times ] 2008-04-13 12:33:00 PDT LOG: incomplete startup packet 2008-04-13 12:33:00 PDT LOG: received fast shutdown request 2008-04-13 12:33:12 PDT FATAL: the database system is shutting down [ repeat a dozen times ] 2008-04-13 12:34:00 PDT LOG: received immediate shutdown request 2008-04-13 12:34:02 PDT LOG: could not load root certificate file "root.crt": No such file or directory 2008-04-13 12:34:02 PDT DETAIL: Will not verify client certificates. 2008-04-13 12:34:20 PDT LOG: could not create IPv6 socket: Address family not supported by protocol 2008-04-13 12:34:20 PDT LOG: could not resolve "localhost": Name or service not known 2008-04-13 12:34:20 PDT LOG: disabling statistics collector for lack of working socket 2008-04-13 12:34:20 PDT WARNING: autovacuum not started because of misconfiguration 2008-04-13 12:34:20 PDT HINT: Enable options "stats_start_collector" and "stats_row_level". 2008-04-13 12:34:20 PDT LOG: database system was interrupted at 2008-04-13 12:22:44 PDT 2008-04-13 12:34:20 PDT LOG: checkpoint record is at 0/594FDF58 2008-04-13 12:34:20 PDT LOG: redo record is at 0/5946B830; undo record is at 0/0; shutdown FALSE 2008-04-13 12:34:20 PDT LOG: next transaction ID: 0/2979312; next OID: 106497 2008-04-13 12:34:20 PDT LOG: next MultiXactId: 1; next MultiXactOffset: 0 2008-04-13 12:34:20 PDT LOG: database system was not properly shut down; automatic recovery in progress 2008-04-13 12:34:20 PDT LOG: redo starts at 0/5946B830 2008-04-13 12:34:21 PDT LOG: incomplete startup packet 2008-04-13 12:34:21 PDT LOG: record with zero length at 0/5957A3EC 2008-04-13 12:34:21 PDT LOG: redo done at 0/5957A3C4 2008-04-13 12:34:21 PDT LOG: database system is ready Any advice on how I can get this bug identified and squashed? I suspect it's in the create/drop [database,role,schema]. I've used postgres for 7 years without issues at this point. The only thing different now are my usage patterns. Since I'm offering a database as a service to my users I'm adding and dropping databases roles and schemas constantly. Thanks
Re: [BUGS] tracking down a crash bug
"Orion Henry" <[EMAIL PROTECTED]> writes: > 2008-04-13 12:26:48 PDT LOG: background writer process (PID 965) was > terminated by signal 9 Turn off memory overcommit. 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 #4101: Fails to start when transaction log on another drive
Mikel Lindsaar wrote: linkd d:\PostgreSQL\8.3\data\pg_xlog "C:\Program Files\PostgreSQL\transaction_log\pg_xlog" The correct xlog path is $PGDATA\pg_xlog. Normally, it is 'C:\Program Files\PostgreSQL\X.X\data\pg_xlog'. -- Euler Taveira de Oliveira http://www.timbira.com/ -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
