Re: [BUGS] BUG #7819: missing chunk number 0 for toast value 1235919 in pg_toast_35328

2013-02-01 Thread Tom Lane
Pius Chan writes: > Thanks for your prompt response. Yeah, I should have provided you with my > testing scripts. BTW, during numerous tests, I felt that if there is no long > holding transaction (the one used for middle-tier service master/slave > failover), the database server is much quicker

Re: [BUGS] BUG #7819: missing chunk number 0 for toast value 1235919 in pg_toast_35328

2013-02-01 Thread Pius Chan
: Friday, February 01, 2013 11:41 AM To: Pius Chan Cc: pgsql-bugs@postgresql.org; Frank Moi; Ken Yu; Vincent Lasmarias; Vladimir Kosilov Subject: Re: [BUGS] BUG #7819: missing chunk number 0 for toast value 1235919 in pg_toast_35328 Pius Chan writes: > The ERROR happened again. After several days

Re: [BUGS] BUG #7819: missing chunk number 0 for toast value 1235919 in pg_toast_35328

2013-02-01 Thread Tom Lane
Pius Chan writes: > The ERROR happened again. After several days of investigation and testing, I > can now reproduce the ERROR in my testing environment. The reason why the > ERROR used to happen in a certain time period is that our report batch jobs > run in that period and the batch job can m

Re: [BUGS] BUG #7819: missing chunk number 0 for toast value 1235919 in pg_toast_35328

2013-01-31 Thread Pius Chan
From: Tom Lane [t...@sss.pgh.pa.us] Sent: Tuesday, January 22, 2013 8:14 PM To: Pius Chan Cc: pgsql-bugs@postgresql.org Subject: Re: [BUGS] BUG #7819: missing chunk number 0 for toast value 1235919 in pg_toast_35328 Pius Chan writes: > Hi Tom, > Yes, we start seeing this ERROR after upgrad

Re: [BUGS] BUG #7819: missing chunk number 0 for toast value 1235919 in pg_toast_35328

2013-01-23 Thread Pius Chan
help. Pius From: Tom Lane [t...@sss.pgh.pa.us] Sent: Tuesday, January 22, 2013 8:14 PM To: Pius Chan Cc: pgsql-bugs@postgresql.org Subject: Re: [BUGS] BUG #7819: missing chunk number 0 for toast value 1235919 in pg_toast_35328 Pius Chan writes: > Hi

Re: [BUGS] BUG #7819: missing chunk number 0 for toast value 1235919 in pg_toast_35328

2013-01-22 Thread Tom Lane
Pius Chan writes: > Hi Tom, > Yes, we start seeing this ERROR after upgrade to 9.1.7. The ERROR is from the > "cluster jms_messages" command. Last night, the ERROR happened three times: > (1) at 00:20:01 > ERROR: missing chunk number 0 for toast value 1239124 in pg_toast_35328 > (2) at 00:25

Re: [BUGS] BUG #7819: missing chunk number 0 for toast value 1235919 in pg_toast_35328

2013-01-22 Thread Pius Chan
:53 PM To: Pius Chan Cc: pgsql-bugs@postgresql.org Subject: Re: [BUGS] BUG #7819: missing chunk number 0 for toast value 1235919 in pg_toast_35328 pc...@contigo.com writes: > We just upgraded from PostgreSQL 9.1.3 to 9.1.7 last week. Are you saying this error started to appear just after the

Re: [BUGS] BUG #7819: missing chunk number 0 for toast value 1235919 in pg_toast_35328

2013-01-21 Thread Pius Chan
Yes, I did not see this ERROR before the upgrade. Thanks, Pius From: Tom Lane [t...@sss.pgh.pa.us] Sent: Monday, January 21, 2013 5:53 PM To: Pius Chan Cc: pgsql-bugs@postgresql.org Subject: Re: [BUGS] BUG #7819: missing chunk number 0 for toast value

Re: [BUGS] BUG #7819: missing chunk number 0 for toast value 1235919 in pg_toast_35328

2013-01-21 Thread Tom Lane
pc...@contigo.com writes: > We just upgraded from PostgreSQL 9.1.3 to 9.1.7 last week. Are you saying this error started to appear just after the upgrade? Or was it there before? > In our database > cluster, one database is used by the Java Message Service (JMS) system. One > table in the databa

[BUGS] BUG #7819: missing chunk number 0 for toast value 1235919 in pg_toast_35328

2013-01-21 Thread pchan
The following bug has been logged on the website: Bug reference: 7819 Logged by: Pius Chan Email address: pc...@contigo.com PostgreSQL version: 9.1.7 Operating system: CentOS (Linux version 2.6.32-220 Description: We just upgraded from PostgreSQL 9.1.3 to 9.1.7 last w