[HACKERS] can you have any idea about toast missing chunk issu resolution
Hi all, We are getting following error message on doing any action on the table like(Select or open from pgadmin). Please suggest. ERROR: missing chunk number 0 for toast value 54787 in pg_toast_2619 ** Error ** ERROR: missing chunk number 0 for toast value 54787 in pg_toast_2619 SQL state: XX000 CREATE TABLE mm_activealarm ( alarm_id integer NOT NULL, source_address character varying(255) NOT NULL, alarm_instance_id integer NOT NULL, alarm_raise_time bigint, alarm_update_time bigint, alarm_cease_time bigint, alarm_count integer, alarm_severity integer NOT NULL, source_type character varying(40) NOT NULL, alarm_state integer NOT NULL, event_type integer, notification_id integer NOT NULL, probable_cause integer NOT NULL, specific_problem integer NOT NULL, alarm_additional_text character varying(10240), alarm_ack_time bigint, alarm_ack_user character varying(100) NOT NULL, alarm_ack_system character varying(100) NOT NULL, alarm_proposed_repair_action character varying(10240) NOT NULL, CONSTRAINT mm_activealarm_pk PRIMARY KEY (alarm_id, source_address) USING INDEX TABLESPACE mgrdata ) WITH ( OIDS=FALSE ) TABLESPACE mgrdata; ALTER TABLE ss_activealarm OWNER TO ss_super; Regards Tarkeshwar
Re: [HACKERS] Postgres TR for missing chunk
Hello friends, Thanks for your useful inputs. We are facing this issue and want to analyse this through logging. can you please share a sample Postgres config file to enable max logging with syslog support? What should be the debug level so that I can capture the failure information? Regards Tarkeshwar -Original Message- From: Tom Lane [mailto:t...@sss.pgh.pa.us] Sent: 16 December 2014 22:25 To: Jaime Casanova Cc: M Tarkeshwar Rao; PostgreSQL-development Subject: Re: [HACKERS] Postgres TR for missing chunk Jaime Casanova ja...@2ndquadrant.com writes: You know, that toast table name ringed a bell. Look at this thread maybe this is your problem, and if it is then is already fixed and you should update. http://www.postgresql.org/message-id/12138.1336019...@sss.pgh.pa.us That was about transient failures though, not persistent ones, which is what the OP seems to be claiming he's getting. Btw, when giving a bug report you should start but saying your PostgreSQL's version and explain what you did based on Google's wisdom Yeah. regards, tom lane -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
Re: [HACKERS] Postgres TR for missing chunk
Hello Friends, Can you please tell me the how can I track the which bugs are fixed in which release and when they will be fixed, If I want to track the analysis and status of the bug raised on Postgres. Can I get this information. From last few days we are struggling with following issue: 1. Additionally we found that few operations on this table is getting failed like select or truncate and a more specific error is thrown as per below:- ERROR: missing chunk number 0 for toast value 54787 in pg_toast_2619 ** Error ** We done all the suggested things on Google but not able to resolve it. I want to know how to avoid this issue? Can you please suggest upto when following bugs will be resolved? There are the known Bug on Postgres. Bugs detail are mentioned below. BUG #9187: corrupt toast tables http://www.postgresql.org/message-id/30154.1392153...@sss.pgh.pa.us http://www.postgresql.org/message-id/cafj8praufpttn5+ohfqpbcd1jzkersck51uakhcwd8nt4os...@mail.gmail.com http://www.postgresql.org/message-id/20140211162408.2713.81...@wrigleys.postgresql.org BUG #7819: missing chunk number 0 for toast value 1235919 in pg_toast_35328 http://www.postgresql.org/message-id/C62EC84B2D3CF847899CCF4B589CCF70B20AA08F@BBMBX.backbone.local Thanks !! Tarkeshwar
[HACKERS] issue in postgresql 9.1.3 in using arrow key in Solaris platform
Hi all, We are facing following issue in postgresql 9.1.3 in using arrow key in Solaris platform. Can you please help us to resolve it or any new release has fix for this or any workaround for this? issue: psql client generates a core when up arrow is used twice. Platfrom: Solaris X86 Steps to reproduce: = 1. Login to any postgres database 2. execute any quer say \list 3. press up arrow twice. 4. segmentation fault occurs and core is generated. Also session is terminated. PLease find example below # ./psql -U super -d mgrdb Password for user super: psql (9.1.3) Type help for help. mgrdb=# \l List of databases Name| Owner | Encoding | Collate |Ctype| Access privileg es ---+--+--+-+-+-- - mgrdb | postgres | UTF8 | en_US.UTF-8 | en_US.UTF-8 | postgres | postgres | UTF8 | en_US.UTF-8 | en_US.UTF-8 | template0 | postgres | UTF8 | en_US.UTF-8 | en_US.UTF-8 | =c/postgres + | | | | | postgres=CTc/post gres template1 | postgres | UTF8 | en_US.UTF-8 | en_US.UTF-8 | =c/postgres + | | | | | postgres=CTc/post gres (4 rows) mgrdb=# mgrdb=# select count(1) from operator_msm;Segmentation Fault (core dumped) Regards Tarkeshwar
[HACKERS] Insert query hangs
Hi all, We have a table in a database DB1 with name Test. We imported this database from another machine. When I fire insert statement it is going in the hang state. Then I created another table with same structure and with same data within it as in table Test. Then I fired the insert statement. It is working fine. I am not able find the reason for this. Can you please help me out on this. This scenario easily reproducible. I have a standalone system and postgresql 9.1 installed on it. Regards Tarkeshwar -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
[HACKERS] FW: [postgres-discuss] Insert query hangs
I have the hang issue in Postgres, When I am going to insert into record in a table. Table structure is enclosed in the discussion. Also we found the issue with unique indexes. When I removed the unique index insert operation is working fine. I need help from this core group that weather this is the bug in the Postgres code or we are using unique index wrongly. Regards Tarkeshwar From: Niklas Andersson Sent: 09 July 2014 18:21 To: M Tarkeshwar Rao; Leo Zhou; postgres-disc...@mailman.lmera.ericsson.se Subject: RE: [postgres-discuss] Insert query hangs I wouldn't advice you to drop the indexes in a production environment, as they are usually very important to get fast queries. Your index doesn't seem to be of much use though, as it looks like you are only indexing one single column that is an integer. It seems as it is not needed. Usually you use indexes with two or more columns to speed up queries, or you join on those columns. If you want to make sure that that column is unique, I would advice you to define it as a primary key. You could also use the keyword unique, but in this case I would prefer to define it as a primary key. Then in order to always get a new, unique integer as a primary key, I would suggest you have a look at CREATE SEQUENCE. The syntax comes from how Oracle does it and it works very nice [1] But, this doesn't explain why your current index is causing problems, becuase it _shouldnt_ ;-/ I think you would need some tools to have a check on the server load. Or have a look at how EXPLAIN works, Unfortunately I don't have that deep competence :-( [1] http://www.postgresql.org/docs/8.1/static/sql-createsequence.html Regards, Niklas From: M Tarkeshwar Rao Sent: Wednesday, 09 July 2014 2:29 PM To: Niklas Andersson; Leo Zhou; postgres-disc...@mailman.lmera.ericsson.semailto:postgres-disc...@mailman.lmera.ericsson.se Subject: RE: [postgres-discuss] Insert query hangs What should I do resolve this issue? Change the structure of Table or I should not create the index. From: Niklas Andersson Sent: 09 July 2014 17:58 To: M Tarkeshwar Rao; Leo Zhou; postgres-disc...@mailman.lmera.ericsson.semailto:postgres-disc...@mailman.lmera.ericsson.se Subject: RE: [postgres-discuss] Insert query hangs Yes, and the more data, the longer it takes to rebuild the index. This is why you drop the indexes during certain copy operations, if you have indexes enabled the copy would take forever. Regards, Niklas From: M Tarkeshwar Rao Sent: Wednesday, 09 July 2014 2:22 PM To: Niklas Andersson; Leo Zhou; postgres-disc...@mailman.lmera.ericsson.semailto:postgres-disc...@mailman.lmera.ericsson.se Subject: RE: [postgres-discuss] Insert query hangs Fine now I understand why it is taking time. Is it possible that insert operation will take time when unique index is already created on the table and table has some data within it? From: Niklas Andersson Sent: 09 July 2014 17:20 To: M Tarkeshwar Rao; Leo Zhou; postgres-disc...@mailman.lmera.ericsson.semailto:postgres-disc...@mailman.lmera.ericsson.se Subject: RE: [postgres-discuss] Insert query hangs Can this be of help [1]? [1] http://www.postgresql.org/docs/9.2/static/sql-createindex.html#SQL-CREATEINDEX-CONCURRENTLY Regards, Niklas From: M Tarkeshwar Rao Sent: Wednesday, 09 July 2014 1:41 PM To: Niklas Andersson; Leo Zhou; postgres-disc...@mailman.lmera.ericsson.semailto:postgres-disc...@mailman.lmera.ericsson.se Subject: RE: [postgres-discuss] Insert query hangs CREATE TABLE eventlogentry ( tableindex integer, object character varying(80), method character varying(80), bgwuser character varying(80), time character(23), realuser character varying(80), host character varying(80), application character varying(80) ) WITH ( OIDS=FALSE ) TABLESPACE mmdata; ALTER TABLE eventlogentry OWNER TO mmsuper; GRANT ALL ON TABLE eventlogentry TO mmsuper; GRANT SELECT ON TABLE eventlogentry TO report; CREATE UNIQUE INDEX ind1_eventlogentry ON eventlogentry USING btree (tableindex ) TABLESPACE mmindex; I am sharing the table structure. When we removed the unique index it is working fine. And when created normal index(not unique) it is working fine. After removing unique index we tried to recreate it but it is giving following infinite logs : concurrent insert in progress within table eventlogentry caveat when building a unique index concurrently is that the uniqueness constraint is already being enforced against other transactions when the second table scan begins Regards Tarkeshwar From: Niklas Andersson Sent: 09 July 2014 16:10 To: M Tarkeshwar Rao; Leo Zhou; postgres-disc...@mailman.lmera.ericsson.semailto:postgres-disc...@mailman.lmera.ericsson.se Subject: RE: [postgres-discuss] Insert query hangs Hi, You have some info on checking on corrupt tables here [1
