ERROR: missing chunk number 0 for toast value while using logical decoder.\

From: sudalai <sudalait2(at)gmail(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: ERROR: missing chunk number 0 for toast value while using logical decoder.\
Date: 2016-06-23 06:38:25
Message-ID: 1466663905344-5909194.post@n5.nabble.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general


I am using PostgresSQL 9.5.0.
I have customized :
https://github.com/michaelpq/pg_plugins/tree/master/decoder_raw to get
result as json. It works fine. suddenly i getting below exception while
consuming or peeking changes through that logical slot.
Does postgres removed the rows needed for that slot??
Kindly help me to find the problem.

db=# select * from pg_logical_slot_get_changes('lslot',NULL,1);
ERROR: missing chunk number 0 for toast value 857563 in pg_toast_782254
CONTEXT: slot "lslot", output plugin "rep_slot", in the change callback,
associated LSN 2E/3C26D6F0

select * from pg_class where relname like 'pg_toast_782254';
-[ RECORD 1 ]-------+----------------
relname | pg_toast_782254
relnamespace | 99
reltype | 782273
reloftype | 0
relowner | 10
relam | 0
relfilenode | 782272
reltablespace | 0
relpages | 464
reltuples | 2066
relallvisible | 464
reltoastrelid | 0
relhasindex | t
relisshared | f
relpersistence | p
relkind | t
relnatts | 3
relchecks | 0
relhasoids | f
relhaspkey | t
relhasrules | f
relhastriggers | f
relhassubclass | f
relrowsecurity | f
relforcerowsecurity | f
relispopulated | t
relreplident | n
relfrozenxid | 1982173
relminmxid | 1
relacl |
reloptions |

Thanks In Advance.

-----
sudalai
--
View this message in context: http://postgresql.nabble.com/ERROR-missing-chunk-number-0-for-toast-value-while-using-logical-decoder-tp5909194.html
Sent from the PostgreSQL - general mailing list archive at Nabble.com.

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Jason Dusek 2016-06-23 06:46:54 client_min_messages and INFO
Previous Message David G. Johnston 2016-06-22 23:07:45 Re: optimizing a query