[BUGS] Disastrous : Server shuts down abnormally
Hi, I am using PostgreSql for Windows.It is running on Cygwin which creates a Unix environment. I am facing this problem when I start the PostgreSql database server and query any of the database. The message (copied below) is flashed on the console.All the processes are terminated and the database server comes down. What might the problem? Is there any configuration settings that I might have missed out?-bwicdb=# select * from batch_instance;FATAL 2: open of /usr/share/postgresql/data/pg_clog/0C81 failed: No such file or directory FATAL 2: open of /usr/share/postgresql/data/pg_clog/0C81 failed: No such file or directoryserver closed the connection unexpectedly This probably means the server terminated abnormally before or while processing the request.The connection to the server was lost. Attempting reset: DEBUG: server process (pid 1328) exited with exit code 2DEBUG: terminating any other active server processesNOTICE: Message from PostgreSQL backend: The Postmaster has informed me that some other backend died abnormally and possibly corrupted shared memory. I have rolled back the current transaction and am going to terminate your database system connection and exit. Please reconnect to the database system and repeat your query.NOTICE: Message from PostgreSQL backend: The Postmaster has informed me that some other backend died abnormally and possibly corrupted shared memory. I have rolled back the current transaction and am going to terminate your database system connection and exit. Please reconnect to the database system and repeat your query.Failed.!# DEBUG: all server processes terminated; reinitializing shared memory and semaphores IpcMemoryCreate: shmget(key=5432001, size=1441792, 03600) failed: Not enough core This error usually means that PostgreSQL's request for a shared memory segment exceeded available memory or swap space.To reduce the request size (currently 1441792 bytes), reduce PostgreSQL's shared_buffers parameter (currently 64) and/orits max_connections parameter (currently 32). The PostgreSQL Administrator's Guide contains more information about shared memory configuration.- I have gone through the PostgreSQL Administrator's Guide and tried to changes the parameters in the postgresql.conf file but the persists. Eagerly awaiting a reply.Thanks and Regards, Kallol NandiSoftware EngineerAutomated Workflow Pvt. Ltd. Transforming the Way People Work... Phone: +91-80-547 4102 / 548 2271Fax: +91-80-5467241Email: [EMAIL PROTECTED]Visit us @ http://www.aworkflow.com "The information in this email is confidential, and intended solely for the addressee. Access to this email by anyone else is unauthorized. If you are the addressee, the contents of this email are intended for your use only and it must not be forwarded to any third party, without first obtaining written authorization from the originator, or AWPL and its subsidiaries. It may contain information, which is confidential and legally privileged, and the same shall not be used, or dealt with, by any third party, in any manner whatsoever, without the specific consent of AWPL and its subsidiaries or its Group Companies. The opinions expressed are those of the sender, and do not necessarily reflect those of the AWPL Group."
Re: [BUGS] Postgresql 7.3.2 Crash
On Tue, 25 Mar 2003, Stephan Szabo wrote: > Okay, I think I've localized the cause (but not a fix). > > > name_id bigint not null default 0, > > I think the problem occurs with of the hack (mentioned in the last mail) > because the default expression is of a different type. I think it occurs > specifically because the default expression is of a by value type and the > real type is by reference, but I haven't gone through enough tests to be > sure (it works if I make the default a bigint, a timestamp column with a > timestamptz expression works but an abstime doesn't) > > Short term workaround is to make the default expression of the same type > as the column rather than merely something that can be converted to > that type. Well, you're right, here is my workaround: -- purpose: workaround the dumb value to bigint conversion of postgresql :) -- usage getmebigint(int); drop FUNCTION getmebigint(int); CREATE FUNCTION getmebigint(int) RETURNS bigint AS 'DECLARE id bigint; BEGIN select $1 into id; RETURN id; END;' language 'plpgsql'; And in table definitions you use getmebigint(0) that makes the transformation between value type and bigint type name_id bigint not null default getmebigint(0), Awful but is working until you'll find the problem. Question: there isn't any cast operator like this?: name_id bigint not null default bigint(0) Anyway, thankz for the fast reply. Regards, Adrian Pop ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
Re: [BUGS] Bug #920: The PostgreSql Server goes down
[EMAIL PROTECTED] writes: > FATAL 2: open of /usr/share/postgresql/data/pg_clog/0C81 failed: No such file or > directory This indicates corrupted data --- specifically, a trashed transaction ID in a row header. In all the cases I've been able to examine, this was just the first symptom of more widespread corruption (usually, a whole disk page is trashed). I recommend checking for hardware problems; you may have bad RAM or a flaky disk drive or cable. regards, tom lane ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
Re: [BUGS] Postgresql 7.3.2 Crash
On Wed, 26 Mar 2003, Adrian Pop wrote: > > > Okay, I think I've localized the cause (but not a fix). > > > > > name_id bigint not null default 0, > > > > I think the problem occurs with of the hack (mentioned in the last mail) > > because the default expression is of a different type. I think it occurs > > specifically because the default expression is of a by value type and the > > real type is by reference, but I haven't gone through enough tests to be > > sure (it works if I make the default a bigint, a timestamp column with a > > timestamptz expression works but an abstime doesn't) > > > > Short term workaround is to make the default expression of the same type > > as the column rather than merely something that can be converted to > > that type. > > And in table definitions you use getmebigint(0) that makes the > transformation between value type and bigint type > > name_id bigint not null default getmebigint(0), > > Awful but is working until you'll find the problem. > > Question: there isn't any cast operator like this?: > name_id bigint not null default bigint(0) The conversion/cast would be one of int8(0), 0::bigint, 0::int8 or CAST(0 as bigint) ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
[BUGS] Relation n does not exist when trying to ad a foregin key
Dear all: I am having this error when I try to add a foreign key: ERROR: Relation n does not exist Here is the command: test=# alter table cep_bairro add FOREIGN KEY (cod_localidade) REFERENCES cidade (cod_localidade); NOTICE: ALTER TABLE will create implicit trigger(s) for FOREIGN KEY check(s) ERROR: Relation 107890740 does not exist On the other hand, the same command works for another table, when I try to link to the same table: test=# alter table cep_logra add FOREIGN KEY (cod_localidade) REFERENCES cidade (cod_localidade); NOTICE: ALTER TABLE will create implicit trigger(s) for FOREIGN KEY check(s) ALTER TABLE Time: 234175.99 ms What is is going? These 3 tables (cep_bairro, cep_logra and cidade) where changed a lot, either by being recriated or via alter table. Table cidade has its primary key changed, but both related tables (cep_bairro, cep_logra) have their corresponded field also changed. Thanks. ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
[BUGS] PostgreSQL book recommendation?
Hi I'm thinking of buying "Practical PostgreSQL" from O'Reilly. Has anyone got any comments on this book? Can anyone suggest alternatives? My level is best described as "intermediate". Thanks in advance! ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
[BUGS] PostgreSql Server Problem
Hi, I am facing this problem when I start the PostgreSql database server and query any of the database. What might the problem? Is there any configuration settings that I might have missed out? Please help. - bwicdb=# select * from batch_instance; FATAL 2: open of /usr/share/postgresql/data/pg_clog/0C81 failed: No such file or directory FATAL 2: open of /usr/share/postgresql/data/pg_clog/0C81 failed: No such file or directory server closed the connection unexpectedly This probably means the server terminated abnormally before or while processing the request. The connection to the server was lost. Attempting reset: DEBUG: server process (pid 1328) exited with exit code 2 DEBUG: terminating any other active server processes NOTICE: Message from PostgreSQL backend: The Postmaster has informed me that some other backend died abnormally and possibly corrupted shared memory. I have rolled back the current transaction and am going to terminate your database system connection and exit. Please reconnect to the database system and repeat your query. NOTICE: Message from PostgreSQL backend: The Postmaster has informed me that some other backend died abnormally and possibly corrupted shared memory. I have rolled back the current transaction and am going to terminate your database system connection and exit. Please reconnect to the database system and repeat your query. Failed. !# DEBUG: all server processes terminated; reinitializing shared memory and semaphores IpcMemoryCreate: shmget(key=5432001, size=1441792, 03600) failed: Not enough core This error usually means that PostgreSQL's request for a shared memory segment exceeded available memory or swap space. To reduce the request size (currently 1441792 bytes), reduce PostgreSQL's shared_buffers parameter (currently 64) and/or its max_connections parameter (currently 32). The PostgreSQL Administrator's Guide contains more information about shared memory configuration. - Eagerly awaiting a reply. Thanks and Regards, Kallol. mail2web - Check your email from the web at http://mail2web.com/ . ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
[BUGS] Bug #921: Default value not available in RULE
A.Bhuvaneswaran ([EMAIL PROTECTED]) reports a bug with a severity of 3 The lower the number the more severe it is. Short Description Default value not available in RULE Long Description I as using postgresql 7.2.3. The default value of a column is not available in the INSERT RULE. The same value is available in the trigger which is triggered before insert. Eventhough the rule is executed before the event, the default value of a column must be available in the INSERT RULE. Isn't it? Sample Code test_pg=# CREATE TABLE a (id int, ctime timestamp default now()); CREATE test_pg=# CREATE TABLE a_log (id int, ctime timestamp); CREATE test_pg=# CREATE RULE a_rule as on insert to a do (insert into a_log (id, ctime) values (new.id, new.ctime)); CREATE test_pg=# INSERT INTO a VALUES (1); INSERT 14353487 1 test_pg=# SELECT * from a; id | ctime +-- 1 | 2003-03-27 10:14:51.139185+05:30 (1 row) test_pg=# SELECT * from a_log; id | ctime +--- 1 | (1 row) test_pg=# No file was uploaded with this report ---(end of broadcast)--- TIP 3: 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: [BUGS] Bug #921: Default value not available in RULE
[EMAIL PROTECTED] writes: > Default value not available in RULE > I as using postgresql 7.2.3. Update to 7.3.*. regards, tom lane ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faqs/FAQ.html
