pg.ddx.io  pgsql-general@postgresql.org mailing list archive  
help / color / mirror / Atom feed
ERROR: missing chunk number 0 for toast value 14227980
24+ messages / 10 participants
[nested] [flat]

* ERROR: missing chunk number 0 for toast value 14227980
@ 2004-07-07 21:05 Diogo Biazus <diogob@gmail.com>
  2004-07-07 21:40 ` Re: ERROR: missing chunk number 0 for toast value 14227980 Chris Smith <cdsmith@twu.net>
  0 siblings, 1 reply; 24+ messages in thread

From: Diogo Biazus @ 2004-07-07 21:05 UTC (permalink / raw)
  To: pgsql-general

Hi, can anyone help me with this error: ERROR:  missing chunk number 0
for toast value 14227980

Is there a solution?

-- 
Diogo Biazus
diogob@gmail.com
http://www.postgresql.org.br



^ permalink  raw  reply  [nested|flat] 24+ messages in thread

* Re: ERROR: missing chunk number 0 for toast value 14227980
  2004-07-07 21:05 ERROR: missing chunk number 0 for toast value 14227980 Diogo Biazus <diogob@gmail.com>
@ 2004-07-07 21:40 ` Chris Smith <cdsmith@twu.net>
  0 siblings, 0 replies; 24+ messages in thread

From: Chris Smith @ 2004-07-07 21:40 UTC (permalink / raw)
  To: Diogo Biazus <diogob@gmail.com>; pgsql-general

Diogo Biazus wrote:
> Hi, can anyone help me with this error: ERROR:  missing chunk number 0
> for toast value 14227980
>
> Is there a solution?

When I ran into that error, it was apparently due to bugs in the Linux IDE
driver for our disk.  In your case, it may be something different; I can't say
for sure.  Once the primary problem is solved, the only solution seems to be
to dump the table, drop it, and then restore from the dump.

-- 
www.designacourse.com
The Easiest Way to Train Anyone... Anywhere.

Chris Smith - Lead Software Developer/Technical Trainer
MindIQ Corporation




^ permalink  raw  reply  [nested|flat] 24+ messages in thread

* ERROR:  missing chunk number 0 for toast value 382548694 in pg_toast_847386
@ 2011-02-28 00:25 Michael Harris <michael.harris@ericsson.com>
  2011-02-28 04:06 ` Re: ERROR: missing chunk number 0 for toast value 382548694 in pg_toast_847386 Vibhor Kumar <vibhor.kumar@enterprisedb.com>
  0 siblings, 1 reply; 24+ messages in thread

From: Michael Harris @ 2011-02-28 00:25 UTC (permalink / raw)
  To: pgsql-general

Hi,

We have a PG 8.4 database approx 5TB in size.

We were recently testing our restore procedure against our latest dump. The dumps are taken using the Continuous Archiving method with base dumps taken using tar. Our tar script is set up to ignore missing/modified files but should stop on all other errors.

We are testing the restore on a completely separate machine of a similar spec to the server on which the dumps are made.

On our first attempt we were using PG 8.4.0. We struck problems on restore with the error 'Unexpected timeline ID 0 in log file'. After some googling we identified that this was a known bug in PG 8.4.0 so we upgraded the target machine to 8.4.7 and began the recovery again.

On the second attempt the recovery went through smoothly. However, after starting the application again we started to get the following error:

ERROR:  missing chunk number 0 for toast value 382548694 in pg_toast_847386

The table it is trying to access is one in which our application stores various schema information that is used each time the application starts up.

As far as we know the base dump is good and the DB did not complain about any of the WAL files. We are now nervous that our backups are no good, so we want to get to the bottom of it. What can be the reason that these backups are not restoring properly?

Thanks in advance,

Regards
Mike Harris




^ permalink  raw  reply  [nested|flat] 24+ messages in thread

* Re: ERROR: missing chunk number 0 for toast value 382548694 in pg_toast_847386
  2011-02-28 00:25 ERROR:  missing chunk number 0 for toast value 382548694 in pg_toast_847386 Michael Harris <michael.harris@ericsson.com>
@ 2011-02-28 04:06 ` Vibhor Kumar <vibhor.kumar@enterprisedb.com>
  2011-02-28 04:16   ` Re: ERROR:  missing chunk number 0 for toast value 382548694 in pg_toast_847386 Michael Harris <michael.harris@ericsson.com>
  0 siblings, 1 reply; 24+ messages in thread

From: Vibhor Kumar @ 2011-02-28 04:06 UTC (permalink / raw)
  To: Michael Harris <michael.harris@ericsson.com>; +Cc: pgsql-general


On Feb 28, 2011, at 5:55 AM, Michael Harris wrote:

> ERROR:  missing chunk number 0 for toast value 382548694 in pg_toast_847386



This seems more like a corrupted toast table.

Did you try to reindex the pg_toast_847386?
REINDEX table pg_toast.pg_toast_847386;
VACUUM ANALYZE <tablename>;


Thanks & Regards,
Vibhor Kumar
vibhor.kumar@enterprisedb.com
Blog:http://vibhork.blogspot.com




^ permalink  raw  reply  [nested|flat] 24+ messages in thread

* Re: ERROR:  missing chunk number 0 for toast value 382548694 in pg_toast_847386
  2011-02-28 00:25 ERROR:  missing chunk number 0 for toast value 382548694 in pg_toast_847386 Michael Harris <michael.harris@ericsson.com>
  2011-02-28 04:06 ` Re: ERROR: missing chunk number 0 for toast value 382548694 in pg_toast_847386 Vibhor Kumar <vibhor.kumar@enterprisedb.com>
@ 2011-02-28 04:16   ` Michael Harris <michael.harris@ericsson.com>
  2011-02-28 04:24     ` Re: ERROR: missing chunk number 0 for toast value 382548694 in pg_toast_847386 Vibhor Kumar <vibhor.kumar@enterprisedb.com>
  0 siblings, 1 reply; 24+ messages in thread

From: Michael Harris @ 2011-02-28 04:16 UTC (permalink / raw)
  To: Vibhor Kumar <vibhor.kumar@enterprisedb.com>; +Cc: pgsql-general

>> ERROR:  missing chunk number 0 for toast value 382548694 in
>> pg_toast_847386
> 
> This seems more like a corrupted toast table.
>
> Did you try to reindex the pg_toast_847386?
> REINDEX table pg_toast.pg_toast_847386;
> VACUUM ANALYZE <tablename>;

Hi Vibhor,

Thanks for the suggestion.

We didn't try that yet, even though we did see others recommending this as a solution for similar corruptions in the past. 

The main reason we have not gone down that path that after getting this error we do not have any confidence in the integrity of the rest of the database after performing the restore - maybe there are many more tables with corruption in them.

We are mainly concerned that our backups are valid. The fault does not seem to be present on the original database, only after restoring from the base backup + PITR.

Regards
Mike Harris




^ permalink  raw  reply  [nested|flat] 24+ messages in thread

* Re: ERROR: missing chunk number 0 for toast value 382548694 in pg_toast_847386
  2011-02-28 00:25 ERROR:  missing chunk number 0 for toast value 382548694 in pg_toast_847386 Michael Harris <michael.harris@ericsson.com>
  2011-02-28 04:06 ` Re: ERROR: missing chunk number 0 for toast value 382548694 in pg_toast_847386 Vibhor Kumar <vibhor.kumar@enterprisedb.com>
  2011-02-28 04:16   ` Re: ERROR:  missing chunk number 0 for toast value 382548694 in pg_toast_847386 Michael Harris <michael.harris@ericsson.com>
@ 2011-02-28 04:24     ` Vibhor Kumar <vibhor.kumar@enterprisedb.com>
  2011-02-28 04:43       ` Re: ERROR:  missing chunk number 0 for toast value 382548694 in pg_toast_847386 Michael Harris <michael.harris@ericsson.com>
  0 siblings, 1 reply; 24+ messages in thread

From: Vibhor Kumar @ 2011-02-28 04:24 UTC (permalink / raw)
  To: Michael Harris <michael.harris@ericsson.com>; +Cc: pgsql-general


On Feb 28, 2011, at 9:46 AM, Michael Harris wrote:

> The main reason we have not gone down that path that after getting this error we do not have any confidence in the integrity of the rest of the database after performing the restore - maybe there are many more tables with corruption in them.
May be or may not be.

Did you find anything suspicious in pg_log?
Please share recovery.conf information.


> We are mainly concerned that our backups are valid. The fault does not seem to be present on the original database, only after restoring from the base backup + PITR.


Did you verify base backup (Restoring without PITR) ?

Thanks & Regards,
Vibhor Kumar
vibhor.kumar@enterprisedb.com
Blog:http://vibhork.blogspot.com




^ permalink  raw  reply  [nested|flat] 24+ messages in thread

* Re: ERROR:  missing chunk number 0 for toast value 382548694 in pg_toast_847386
  2011-02-28 00:25 ERROR:  missing chunk number 0 for toast value 382548694 in pg_toast_847386 Michael Harris <michael.harris@ericsson.com>
  2011-02-28 04:06 ` Re: ERROR: missing chunk number 0 for toast value 382548694 in pg_toast_847386 Vibhor Kumar <vibhor.kumar@enterprisedb.com>
  2011-02-28 04:16   ` Re: ERROR:  missing chunk number 0 for toast value 382548694 in pg_toast_847386 Michael Harris <michael.harris@ericsson.com>
  2011-02-28 04:24     ` Re: ERROR: missing chunk number 0 for toast value 382548694 in pg_toast_847386 Vibhor Kumar <vibhor.kumar@enterprisedb.com>
@ 2011-02-28 04:43       ` Michael Harris <michael.harris@ericsson.com>
  2011-02-28 05:57         ` Re: ERROR: missing chunk number 0 for toast value 382548694 in pg_toast_847386 Vibhor Kumar <vibhor.kumar@enterprisedb.com>
  0 siblings, 1 reply; 24+ messages in thread

From: Michael Harris @ 2011-02-28 04:43 UTC (permalink / raw)
  To: Vibhor Kumar <vibhor.kumar@enterprisedb.com>; +Cc: pgsql-general

Hi Vibhor,

>> Did you find anything suspicious in pg_log?

We've been through it all and did not see anything we didn't expect.

>> Please share recovery.conf information.

We did interrupt the restore a few times. The initial recovery.conf file contained only:

restore_command = 'gunzip -c /mnt/dbsbackup/pg_xlog/%f.gz > %p'

Later we decided to replace the recovery command with a wrapper script that would allow us to leave the restore going unattended over the weekend, and complete up until the latest WAL file on the original database (which is still running). We changed the recovery command to:

restore_command = '/var/lib/pgsql/data/db_restore_dm %f %p'

where the script db_restore_dm contained:

#!/usr/bin/perl

use strict;

my ($pg_f, $pg_p) = @ARGV;
exit 1 if $pg_f eq '00000001.history';

my $xlogBackupFile = "/mnt/dbsbackup/pg_xlog/$pg_f.gz";

while (! -f $xlogBackupFile and !$triggered) {
        sleep 2;
}

while (1) {
  system("gunzip -c $xlogBackupFile > $pg_p");
  last if ($? >> 8 == 0);
  sleep 2;
}

We were concerned that shutting down / starting up while recovery is ongoing might cause some problems, but the pg documentation indicates this should be OK and we saw no cause for concern in the pg logs.

> Did you verify base backup (Restoring without PITR) ?

I guess you mean did we restore it up until consistency reached? No so far we have continued restoration until we reached the last WAL file made by the original database.

Regards // Mike


-----Original Message-----
From: Vibhor Kumar [mailto:vibhor.kumar@enterprisedb.com] 
Sent: Monday, 28 February 2011 3:25 PM
To: Michael Harris
Cc: pgsql-general@postgresql.org
Subject: Re: [GENERAL] ERROR: missing chunk number 0 for toast value 382548694 in pg_toast_847386


On Feb 28, 2011, at 9:46 AM, Michael Harris wrote:

> The main reason we have not gone down that path that after getting this error we do not have any confidence in the integrity of the rest of the database after performing the restore - maybe there are many more tables with corruption in them.
May be or may not be.

Did you find anything suspicious in pg_log?
Please share recovery.conf information.


> We are mainly concerned that our backups are valid. The fault does not seem to be present on the original database, only after restoring from the base backup + PITR.


Did you verify base backup (Restoring without PITR) ?

Thanks & Regards,
Vibhor Kumar
vibhor.kumar@enterprisedb.com
Blog:http://vibhork.blogspot.com




^ permalink  raw  reply  [nested|flat] 24+ messages in thread

* Re: ERROR: missing chunk number 0 for toast value 382548694 in pg_toast_847386
  2011-02-28 00:25 ERROR:  missing chunk number 0 for toast value 382548694 in pg_toast_847386 Michael Harris <michael.harris@ericsson.com>
  2011-02-28 04:06 ` Re: ERROR: missing chunk number 0 for toast value 382548694 in pg_toast_847386 Vibhor Kumar <vibhor.kumar@enterprisedb.com>
  2011-02-28 04:16   ` Re: ERROR:  missing chunk number 0 for toast value 382548694 in pg_toast_847386 Michael Harris <michael.harris@ericsson.com>
  2011-02-28 04:24     ` Re: ERROR: missing chunk number 0 for toast value 382548694 in pg_toast_847386 Vibhor Kumar <vibhor.kumar@enterprisedb.com>
  2011-02-28 04:43       ` Re: ERROR:  missing chunk number 0 for toast value 382548694 in pg_toast_847386 Michael Harris <michael.harris@ericsson.com>
@ 2011-02-28 05:57         ` Vibhor Kumar <vibhor.kumar@enterprisedb.com>
  2011-02-28 06:27           ` Re: ERROR:  missing chunk number 0 for toast value 382548694 in pg_toast_847386 Michael Harris <michael.harris@ericsson.com>
  0 siblings, 1 reply; 24+ messages in thread

From: Vibhor Kumar @ 2011-02-28 05:57 UTC (permalink / raw)
  To: Michael Harris <michael.harris@ericsson.com>; +Cc: pgsql-general


On Feb 28, 2011, at 10:13 AM, Michael Harris wrote:

>>> 
>>> Did you find anything suspicious in pg_log?
> 
> We've been through it all and did not see anything we didn't expect.
> 
>>> Please share recovery.conf information.
> 
> We did interrupt the restore a few times. The initial recovery.conf file contained only:
> 
> restore_command = 'gunzip -c /mnt/dbsbackup/pg_xlog/%f.gz > %p'
> 
> Later we decided to replace the recovery command with a wrapper script that would allow us to leave the restore going unattended over the weekend, and complete up until the latest WAL file on the original database (which is still running). We changed the recovery command to:
> 
> restore_command = '/var/lib/pgsql/data/db_restore_dm %f %p'
> 
> where the script db_restore_dm contained:
> 
> #!/usr/bin/perl
> 
> use strict;
> 
> my ($pg_f, $pg_p) = @ARGV;
> exit 1 if $pg_f eq '00000001.history';
> 
> my $xlogBackupFile = "/mnt/dbsbackup/pg_xlog/$pg_f.gz";
> 
> while (! -f $xlogBackupFile and !$triggered) {
>        sleep 2;
> }
> 
> while (1) {
>  system("gunzip -c $xlogBackupFile > $pg_p");
>  last if ($? >> 8 == 0);
>  sleep 2;
> }

Not sure about above wrapper function. However, if you can share some information from pg_log when you have started the restore with backup_label information.

Try following steps:
1. Untar all the gzipped WAL File in One Location
2. Use Following restore command:
    cp <WAL Location>/%f %p


> We were concerned that shutting down / starting up while recovery is ongoing might cause some problems, but the pg documentation indicates this should be OK and we saw no cause for concern in the pg logs.

What options have you used for shutting down?

Thanks & Regards,
Vibhor Kumar
vibhor.kumar@enterprisedb.com
Blog:http://vibhork.blogspot.com




^ permalink  raw  reply  [nested|flat] 24+ messages in thread

* Re: ERROR:  missing chunk number 0 for toast value 382548694 in pg_toast_847386
  2011-02-28 00:25 ERROR:  missing chunk number 0 for toast value 382548694 in pg_toast_847386 Michael Harris <michael.harris@ericsson.com>
  2011-02-28 04:06 ` Re: ERROR: missing chunk number 0 for toast value 382548694 in pg_toast_847386 Vibhor Kumar <vibhor.kumar@enterprisedb.com>
  2011-02-28 04:16   ` Re: ERROR:  missing chunk number 0 for toast value 382548694 in pg_toast_847386 Michael Harris <michael.harris@ericsson.com>
  2011-02-28 04:24     ` Re: ERROR: missing chunk number 0 for toast value 382548694 in pg_toast_847386 Vibhor Kumar <vibhor.kumar@enterprisedb.com>
  2011-02-28 04:43       ` Re: ERROR:  missing chunk number 0 for toast value 382548694 in pg_toast_847386 Michael Harris <michael.harris@ericsson.com>
  2011-02-28 05:57         ` Re: ERROR: missing chunk number 0 for toast value 382548694 in pg_toast_847386 Vibhor Kumar <vibhor.kumar@enterprisedb.com>
@ 2011-02-28 06:27           ` Michael Harris <michael.harris@ericsson.com>
  0 siblings, 0 replies; 24+ messages in thread

From: Michael Harris @ 2011-02-28 06:27 UTC (permalink / raw)
  To: Vibhor Kumar <vibhor.kumar@enterprisedb.com>; +Cc: pgsql-general

Hi Vibhor,

>> Not sure about above wrapper function. However, if you can share some
>> information from pg_log when you have started the restore with
>> backup_label information.

Here it is at the beginning:
[2011-02-25 09:40:11 EST] LOG:  database system was interrupted; last known up at 2011-02-01 01:04:12 EST
[2011-02-25 09:40:11 EST] LOG:  starting archive recovery
[2011-02-25 09:40:11 EST] LOG:  restore_command = 'gunzip -c /mnt/dbsbackup/pg_xlog/%f.gz > %p'
gunzip: /mnt/dbsbackup/pg_xlog/00000001.history.gz: No such file or directory
[2011-02-25 09:40:12 EST] LOG:  restored log file "0000000100006F720000006F.00024AE0.backup" from archive
[2011-02-25 09:40:12 EST] LOG:  restored log file "0000000100006F7200000094" from archive
[2011-02-25 09:40:12 EST] LOG:  restored log file "0000000100006F720000006F" from archive
[2011-02-25 09:40:12 EST] LOG:  automatic recovery in progress
[2011-02-25 09:40:12 EST] LOG:  redo starts at 6F72/6F024AE0, consistency will be reached at 70B1/B75C9AF0
[2011-02-25 09:40:14 EST] LOG:  restored log file "0000000100006F7200000070" from archive
[2011-02-25 09:40:14 EST] LOG:  restored log file "0000000100006F7200000071" from archive
[2011-02-25 09:40:15 EST] LOG:  restored log file "0000000100006F7200000072" from archive

...etc...

We did reach consistency eventually:

[2011-02-25 21:29:28 EST] LOG:  restored log file "00000001000070B1000000B5" from archive
[2011-02-25 21:29:29 EST] LOG:  restored log file "00000001000070B1000000B6" from archive
[2011-02-25 21:29:29 EST] LOG:  restored log file "00000001000070B1000000B7" from archive
[2011-02-25 21:29:29 EST] LOG:  consistent recovery state reached
[2011-02-25 21:29:29 EST] LOG:  restored log file "00000001000070B1000000B8" from archive
[2011-02-25 21:29:30 EST] LOG:  restored log file "00000001000070B1000000B9" from archive
...

>> Try following steps:
>> 1. Untar all the gzipped WAL File in One Location
>> 2. Use Following restore command:
>>     cp <WAL Location>/%f %p

Unfortunately it is not practical to do this, since there are many terabytes of WAL files. They are available on an NFS mounted volume which is accessible from the target machine.

What we can do (and will do if no better suggestions come forward) is to restore again using only the PITR files needed to achieve consistency, ie. up to 70B1/B75C9AF0, a much smaller quantity of WAL files.

>> We were concerned that shutting down / starting up while recovery is
>> ongoing might cause some problems, but the pg documentation indicates
>> this should be OK and we saw no cause for concern in the pg logs.
> What options have you used for shutting down?

We are using Centos and used the supplied init scripts - the actual command is: service postgresql stop, which translates to:

	pg_ctl stop -D '$PGDATA' -s -m fast

Regards
Mike Harris




^ permalink  raw  reply  [nested|flat] 24+ messages in thread

* ERROR: missing chunk number 0 for toast value 1821556134 in pg_toast_17881
@ 2015-05-28 01:28 Tory M Blue <tmblue@gmail.com>
  0 siblings, 0 replies; 24+ messages in thread

From: Tory M Blue @ 2015-05-28 01:28 UTC (permalink / raw)
  To: pgsql-general

Sorry I think I posted this to the wrong group, sent to performance vs
General. My apologies to everyone in perf!

Greetings and salutations.
>
> I've got some weirdness.
>
> Current:
> Postgres 9.3.4
> Slony 2.2.3
> CentOS 6.5
>
> Prior running Postgres 9.1.2 w/slony 2.1.3 CentOS 6.2
>
> I found that if I tried to run a vacuum full on 1 table that I recently
> reindexed (out of possibly 8 tables) that I get this error:
>
> # vacuum full table.ads;
>
> ERROR:  missing chunk number 0 for toast value 1821556134 in pg_toast_17881
>
> If I run a vacuum analyze it completes fine, but I can't run a vacuum full
> without it throwing an error. I seem to be able to query the table and I
> seem to be able to add data to the table and slony seems fine as does
> postgres.
>
> I'm unclear why the vacuum full is failing with this error. I've done some
> searching and there are hints to prior bugs, but I didn't catch anything in
> 9.3.3 to 9.3.7 that talks about this.
>
> My next steps without your fine assistance, will be to drop the table from
> slon and re-add it (meaning it will drop the table completely from this db
> and recreate it from the master (there we can do a vacuum full without
> failure)..
>
> I have already tried to remove the indexes and just create those, but no
> luck.
>
> Ideas?
>
> Thanks
>
> Tory
>
>
>
>

^ permalink  raw  reply  [nested|flat] 24+ messages in thread

* ERROR:  missing chunk number 0 for toast value while using logical decoder.\
@ 2016-06-23 06:38 sudalai <sudalait2@gmail.com>
  2016-06-23 06:53 ` Re: ERROR: missing chunk number 0 for toast value while using logical decoder.\ John R Pierce <pierce@hogranch.com>
  2016-06-23 07:20 ` Re: ERROR: missing chunk number 0 for toast value while using logical decoder.\ Michael Paquier <michael.paquier@gmail.com>
  0 siblings, 2 replies; 24+ messages in thread

From: sudalai @ 2016-06-23 06:38 UTC (permalink / raw)
  To: 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-decode...
Sent from the PostgreSQL - general mailing list archive at Nabble.com.


-- 
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general



^ permalink  raw  reply  [nested|flat] 24+ messages in thread

* Re: ERROR: missing chunk number 0 for toast value while using logical decoder.\
  2016-06-23 06:38 ERROR:  missing chunk number 0 for toast value while using logical decoder.\ sudalai <sudalait2@gmail.com>
@ 2016-06-23 06:53 ` John R Pierce <pierce@hogranch.com>
  2016-06-23 07:20   ` Re: ERROR: missing chunk number 0 for toast value while using logical decoder.\ sudalai <sudalait2@gmail.com>
  1 sibling, 1 reply; 24+ messages in thread

From: John R Pierce @ 2016-06-23 06:53 UTC (permalink / raw)
  To: pgsql-general

On 6/22/2016 11:38 PM, sudalai wrote:
> I am using PostgresSQL 9.5.0.

while this likely has no bearing on your problem, you really should 
upgrade to 9.5.latest, 9.5.3 is out now.    sub version upgrades like 
9.5.0 to 9.5.3 are painless, just upgrade and restart the server with 
the new code.


-- 
john r pierce, recycling bits in santa cruz



-- 
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general



^ permalink  raw  reply  [nested|flat] 24+ messages in thread

* Re: ERROR: missing chunk number 0 for toast value while using logical decoder.\
  2016-06-23 06:38 ERROR:  missing chunk number 0 for toast value while using logical decoder.\ sudalai <sudalait2@gmail.com>
  2016-06-23 06:53 ` Re: ERROR: missing chunk number 0 for toast value while using logical decoder.\ John R Pierce <pierce@hogranch.com>
@ 2016-06-23 07:20   ` sudalai <sudalait2@gmail.com>
  0 siblings, 0 replies; 24+ messages in thread

From: sudalai @ 2016-06-23 07:20 UTC (permalink / raw)
  To: pgsql-general

Hi john,

    PostgreSQL 9.5.0  has bug !!!,  Does 9.5.0 remove  unconsumed toast rows
need for slot?? 
    It is fixed in latest!!!.  

-Sudalai



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


-- 
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general



^ permalink  raw  reply  [nested|flat] 24+ messages in thread

* Re: ERROR: missing chunk number 0 for toast value while using logical decoder.\
  2016-06-23 06:38 ERROR:  missing chunk number 0 for toast value while using logical decoder.\ sudalai <sudalait2@gmail.com>
@ 2016-06-23 07:20 ` Michael Paquier <michael.paquier@gmail.com>
  2016-06-23 07:55   ` Re: ERROR: missing chunk number 0 for toast value while using logical decoder.\ sudalai <sudalait2@gmail.com>
  1 sibling, 1 reply; 24+ messages in thread

From: Michael Paquier @ 2016-06-23 07:20 UTC (permalink / raw)
  To: sudalai <sudalait2@gmail.com>; +Cc: pgsql-general

On Thu, Jun 23, 2016 at 3:38 PM, sudalai <sudalait2@gmail.com> wrote:
>
> 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

A couple of failures in logical decoding have been fixed in 9.5.2 and
9.5.3 but this one is new, still you had better update... The error is
visibly coming from the code of your plugin per the context message.
Do you have an SQL sequence that allows to reproduce the problem? I
recall playing with a couple of data types with my own plugin but I
never noticed that.
-- 
Michael


-- 
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general



^ permalink  raw  reply  [nested|flat] 24+ messages in thread

* Re: ERROR: missing chunk number 0 for toast value while using logical decoder.\
  2016-06-23 06:38 ERROR:  missing chunk number 0 for toast value while using logical decoder.\ sudalai <sudalait2@gmail.com>
  2016-06-23 07:20 ` Re: ERROR: missing chunk number 0 for toast value while using logical decoder.\ Michael Paquier <michael.paquier@gmail.com>
@ 2016-06-23 07:55   ` sudalai <sudalait2@gmail.com>
  2016-06-23 08:03     ` Re: Re: ERROR: missing chunk number 0 for toast value while using logical decoder.\ Michael Paquier <michael.paquier@gmail.com>
  0 siblings, 1 reply; 24+ messages in thread

From: sudalai @ 2016-06-23 07:55 UTC (permalink / raw)
  To: pgsql-general

Thanks for : https://github.com/michaelpq/pg_plugins/tree/master/decoder_raw
I will upgrade my servers to PostgreSQL 9.5.3, but i want to find the
problem. 
Please help me.
I don't have SQL sequence.  
Does anything i can get from server, that will help us to debug the problem?

Here is logical_decoder code:  rep_slot.c
<http://postgresql.nabble.com/file/n5909207/rep_slot.c;  

Thanks in Advance.

-Sudalai



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


-- 
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general



^ permalink  raw  reply  [nested|flat] 24+ messages in thread

* Re: Re: ERROR: missing chunk number 0 for toast value while using logical decoder.\
  2016-06-23 06:38 ERROR:  missing chunk number 0 for toast value while using logical decoder.\ sudalai <sudalait2@gmail.com>
  2016-06-23 07:20 ` Re: ERROR: missing chunk number 0 for toast value while using logical decoder.\ Michael Paquier <michael.paquier@gmail.com>
  2016-06-23 07:55   ` Re: ERROR: missing chunk number 0 for toast value while using logical decoder.\ sudalai <sudalait2@gmail.com>
@ 2016-06-23 08:03     ` Michael Paquier <michael.paquier@gmail.com>
  2016-06-23 12:09       ` Re: ERROR: missing chunk number 0 for toast value while using logical decoder.\ sudalai <sudalait2@gmail.com>
  2016-07-18 07:31       ` Re: ERROR: missing chunk number 0 for toast value while using logical decoder.\ sudalai <sudalait2@gmail.com>
  0 siblings, 2 replies; 24+ messages in thread

From: Michael Paquier @ 2016-06-23 08:03 UTC (permalink / raw)
  To: sudalai <sudalait2@gmail.com>; +Cc: pgsql-general

On Thu, Jun 23, 2016 at 4:55 PM, sudalai <sudalait2@gmail.com> wrote:
> Thanks for : https://github.com/michaelpq/pg_plugins/tree/master/decoder_raw
> I will upgrade my servers to PostgreSQL 9.5.3, but i want to find the
> problem.
> Please help me.
> I don't have SQL sequence.
> Does anything i can get from server, that will help us to debug the problem?
>
> Here is logical_decoder code:  rep_slot.c
> <http://postgresql.nabble.com/file/n5909207/rep_slot.c;

    if (isnull)
        appendStringInfoString(s, "NiLnUlL");   // Printing null as "NiLnUlL"
    //else if (typisvarlena && VARATT_IS_EXTERNAL_ONDISK(origval))
    //  appendStringInfoString(s, "unchanged-toast-datum")
Uncomment that.
-- 
Michael


-- 
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general



^ permalink  raw  reply  [nested|flat] 24+ messages in thread

* Re: ERROR: missing chunk number 0 for toast value while using logical decoder.\
  2016-06-23 06:38 ERROR:  missing chunk number 0 for toast value while using logical decoder.\ sudalai <sudalait2@gmail.com>
  2016-06-23 07:20 ` Re: ERROR: missing chunk number 0 for toast value while using logical decoder.\ Michael Paquier <michael.paquier@gmail.com>
  2016-06-23 07:55   ` Re: ERROR: missing chunk number 0 for toast value while using logical decoder.\ sudalai <sudalait2@gmail.com>
  2016-06-23 08:03     ` Re: Re: ERROR: missing chunk number 0 for toast value while using logical decoder.\ Michael Paquier <michael.paquier@gmail.com>
@ 2016-06-23 12:09       ` sudalai <sudalait2@gmail.com>
  1 sibling, 0 replies; 24+ messages in thread

From: sudalai @ 2016-06-23 12:09 UTC (permalink / raw)
  To: pgsql-general

Thank u. 
The problem is because of the commented line.  I forgot about that. 
Now, I uncommented it. It working fine. 
Thank u very much.

-Sudalai




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


-- 
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general



^ permalink  raw  reply  [nested|flat] 24+ messages in thread

* Re: ERROR: missing chunk number 0 for toast value while using logical decoder.\
  2016-06-23 06:38 ERROR:  missing chunk number 0 for toast value while using logical decoder.\ sudalai <sudalait2@gmail.com>
  2016-06-23 07:20 ` Re: ERROR: missing chunk number 0 for toast value while using logical decoder.\ Michael Paquier <michael.paquier@gmail.com>
  2016-06-23 07:55   ` Re: ERROR: missing chunk number 0 for toast value while using logical decoder.\ sudalai <sudalait2@gmail.com>
  2016-06-23 08:03     ` Re: Re: ERROR: missing chunk number 0 for toast value while using logical decoder.\ Michael Paquier <michael.paquier@gmail.com>
@ 2016-07-18 07:31       ` sudalai <sudalait2@gmail.com>
  2016-07-18 09:09         ` Re: Re: ERROR: missing chunk number 0 for toast value while using logical decoder.\ Michael Paquier <michael.paquier@gmail.com>
  1 sibling, 1 reply; 24+ messages in thread

From: sudalai @ 2016-07-18 07:31 UTC (permalink / raw)
  To: pgsql-general

@micheal, 
    Thanks for your help. It working now.
    But, now I'm getting deadlock, when i peek_changes or get_changes, in
live system. 

    db=#select count(*) from pg_logical_slot_peek_changes('slot',NULL,100); 
/* pid : 25833 */
ERROR:  deadlock detected
DETAIL:  Process 25833 waits for ShareLock on relation 248486 of database
16385; blocked by process 18904.
Process 18904 waits for RowExclusiveLock on relation 257419 of database
16385; blocked by process 25833.
HINT:  See server log for query details.
CONTEXT:  slot "slot", output plugin "rep_slot", in the change callback,
associated LSN CD/EF693310

     Please help me, I am using PostgreSQL 9.5.0. 
     I don't know much in postgres internals. why does peek_changes trying
to take share lock on 248486 (primary key of one table).
     Its postgres logical decoder  takes share lock or output-plugin takes
share lock ?  
     Is there any way i can avoid it?  Please help me.
  
-Sudalai




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


-- 
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general



^ permalink  raw  reply  [nested|flat] 24+ messages in thread

* Re: Re: ERROR: missing chunk number 0 for toast value while using logical decoder.\
  2016-06-23 06:38 ERROR:  missing chunk number 0 for toast value while using logical decoder.\ sudalai <sudalait2@gmail.com>
  2016-06-23 07:20 ` Re: ERROR: missing chunk number 0 for toast value while using logical decoder.\ Michael Paquier <michael.paquier@gmail.com>
  2016-06-23 07:55   ` Re: ERROR: missing chunk number 0 for toast value while using logical decoder.\ sudalai <sudalait2@gmail.com>
  2016-06-23 08:03     ` Re: Re: ERROR: missing chunk number 0 for toast value while using logical decoder.\ Michael Paquier <michael.paquier@gmail.com>
  2016-07-18 07:31       ` Re: ERROR: missing chunk number 0 for toast value while using logical decoder.\ sudalai <sudalait2@gmail.com>
@ 2016-07-18 09:09         ` Michael Paquier <michael.paquier@gmail.com>
  2016-07-18 10:08           ` Re: ERROR: missing chunk number 0 for toast value while using logical decoder.\ sudalai <sudalait2@gmail.com>
  0 siblings, 1 reply; 24+ messages in thread

From: Michael Paquier @ 2016-07-18 09:09 UTC (permalink / raw)
  To: sudalai <sudalait2@gmail.com>; +Cc: pgsql-general

On Mon, Jul 18, 2016 at 4:31 PM, sudalai <sudalait2@gmail.com> wrote:
>      Please help me, I am using PostgreSQL 9.5.0.
>      I don't know much in postgres internals. why does peek_changes trying
> to take share lock on 248486 (primary key of one table).
>      Its postgres logical decoder  takes share lock or output-plugin takes
> share lock ?
>      Is there any way i can avoid it?  Please help me.

No way to say as that's your plugin code. I think that you should look
at your code and grep for ShareLock, trying to find out why this is
taken. My guess is that a lower level of locking could be used,
ShareLock is a strong one, taken when you want to be sure that there
are schema changes for example.
-- 
Michael


-- 
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general



^ permalink  raw  reply  [nested|flat] 24+ messages in thread

* Re: ERROR: missing chunk number 0 for toast value while using logical decoder.\
  2016-06-23 06:38 ERROR:  missing chunk number 0 for toast value while using logical decoder.\ sudalai <sudalait2@gmail.com>
  2016-06-23 07:20 ` Re: ERROR: missing chunk number 0 for toast value while using logical decoder.\ Michael Paquier <michael.paquier@gmail.com>
  2016-06-23 07:55   ` Re: ERROR: missing chunk number 0 for toast value while using logical decoder.\ sudalai <sudalait2@gmail.com>
  2016-06-23 08:03     ` Re: Re: ERROR: missing chunk number 0 for toast value while using logical decoder.\ Michael Paquier <michael.paquier@gmail.com>
  2016-07-18 07:31       ` Re: ERROR: missing chunk number 0 for toast value while using logical decoder.\ sudalai <sudalait2@gmail.com>
  2016-07-18 09:09         ` Re: Re: ERROR: missing chunk number 0 for toast value while using logical decoder.\ Michael Paquier <michael.paquier@gmail.com>
@ 2016-07-18 10:08           ` sudalai <sudalait2@gmail.com>
  2016-07-18 10:55             ` Re: Re: ERROR: missing chunk number 0 for toast value while using logical decoder.\ Michael Paquier <michael.paquier@gmail.com>
  0 siblings, 1 reply; 24+ messages in thread

From: sudalai @ 2016-07-18 10:08 UTC (permalink / raw)
  To: pgsql-general

thank u.
why (select * from pg_logical_slot_peek_changes('slot',NULL,1) )  take share
lock ?  
any  idea ?    

-Sudalai



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


-- 
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general



^ permalink  raw  reply  [nested|flat] 24+ messages in thread

* Re: Re: ERROR: missing chunk number 0 for toast value while using logical decoder.\
  2016-06-23 06:38 ERROR:  missing chunk number 0 for toast value while using logical decoder.\ sudalai <sudalait2@gmail.com>
  2016-06-23 07:20 ` Re: ERROR: missing chunk number 0 for toast value while using logical decoder.\ Michael Paquier <michael.paquier@gmail.com>
  2016-06-23 07:55   ` Re: ERROR: missing chunk number 0 for toast value while using logical decoder.\ sudalai <sudalait2@gmail.com>
  2016-06-23 08:03     ` Re: Re: ERROR: missing chunk number 0 for toast value while using logical decoder.\ Michael Paquier <michael.paquier@gmail.com>
  2016-07-18 07:31       ` Re: ERROR: missing chunk number 0 for toast value while using logical decoder.\ sudalai <sudalait2@gmail.com>
  2016-07-18 09:09         ` Re: Re: ERROR: missing chunk number 0 for toast value while using logical decoder.\ Michael Paquier <michael.paquier@gmail.com>
  2016-07-18 10:08           ` Re: ERROR: missing chunk number 0 for toast value while using logical decoder.\ sudalai <sudalait2@gmail.com>
@ 2016-07-18 10:55             ` Michael Paquier <michael.paquier@gmail.com>
  2016-07-18 11:32               ` Re: ERROR: missing chunk number 0 for toast value while using logical decoder.\ sudalai <sudalait2@gmail.com>
  0 siblings, 1 reply; 24+ messages in thread

From: Michael Paquier @ 2016-07-18 10:55 UTC (permalink / raw)
  To: sudalai <sudalait2@gmail.com>; +Cc: pgsql-general

On Mon, Jul 18, 2016 at 7:08 PM, sudalai <sudalait2@gmail.com> wrote:
> thank u.
> why (select * from pg_logical_slot_peek_changes('slot',NULL,1) )  take share
> lock ?
> any  idea ?

My guess is that this lock comes from your plugin code. Please double-check it.
-- 
Michael


-- 
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general



^ permalink  raw  reply  [nested|flat] 24+ messages in thread

* Re: ERROR: missing chunk number 0 for toast value while using logical decoder.\
  2016-06-23 06:38 ERROR:  missing chunk number 0 for toast value while using logical decoder.\ sudalai <sudalait2@gmail.com>
  2016-06-23 07:20 ` Re: ERROR: missing chunk number 0 for toast value while using logical decoder.\ Michael Paquier <michael.paquier@gmail.com>
  2016-06-23 07:55   ` Re: ERROR: missing chunk number 0 for toast value while using logical decoder.\ sudalai <sudalait2@gmail.com>
  2016-06-23 08:03     ` Re: Re: ERROR: missing chunk number 0 for toast value while using logical decoder.\ Michael Paquier <michael.paquier@gmail.com>
  2016-07-18 07:31       ` Re: ERROR: missing chunk number 0 for toast value while using logical decoder.\ sudalai <sudalait2@gmail.com>
  2016-07-18 09:09         ` Re: Re: ERROR: missing chunk number 0 for toast value while using logical decoder.\ Michael Paquier <michael.paquier@gmail.com>
  2016-07-18 10:08           ` Re: ERROR: missing chunk number 0 for toast value while using logical decoder.\ sudalai <sudalait2@gmail.com>
  2016-07-18 10:55             ` Re: Re: ERROR: missing chunk number 0 for toast value while using logical decoder.\ Michael Paquier <michael.paquier@gmail.com>
@ 2016-07-18 11:32               ` sudalai <sudalait2@gmail.com>
  0 siblings, 0 replies; 24+ messages in thread

From: sudalai @ 2016-07-18 11:32 UTC (permalink / raw)
  To: pgsql-general

Got it. Thank you very much. :)
-Sudalai



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


-- 
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general



^ permalink  raw  reply  [nested|flat] 24+ messages in thread

* ERROR:  missing chunk number 0 for toast value 1563962066 in pg_toast_2619
@ 2023-12-26 20:51 Johnathan Tiamoh <johnathantiamoh@gmail.com>
  2023-12-26 20:58 ` Re: ERROR: missing chunk number 0 for toast value 1563962066 in pg_toast_2619 Adrian Klaver <adrian.klaver@aklaver.com>
  0 siblings, 1 reply; 24+ messages in thread

From: Johnathan Tiamoh @ 2023-12-26 20:51 UTC (permalink / raw)
  To: pgsql-general@lists.postgresql.org

Hello,

Please, I need help to fix this. Can't do anything in the database. This
error keeps popping up.

I have tried to do a pg_dump and the same error keeps coming up.


Thank you
Johnathan Tiamoh

^ permalink  raw  reply  [nested|flat] 24+ messages in thread

* Re: ERROR: missing chunk number 0 for toast value 1563962066 in pg_toast_2619
  2023-12-26 20:51 ERROR:  missing chunk number 0 for toast value 1563962066 in pg_toast_2619 Johnathan Tiamoh <johnathantiamoh@gmail.com>
@ 2023-12-26 20:58 ` Adrian Klaver <adrian.klaver@aklaver.com>
  0 siblings, 0 replies; 24+ messages in thread

From: Adrian Klaver @ 2023-12-26 20:58 UTC (permalink / raw)
  To: Johnathan Tiamoh <johnathantiamoh@gmail.com>; pgsql-general@lists.postgresql.org

On 12/26/23 12:51, Johnathan Tiamoh wrote:
> Hello,
> 
> Please, I need help to fix this. Can't do anything in the database. This 
> error keeps popping up.
> 
> I have tried to do a pg_dump and the same error keeps coming up.

You need to provide answers to the questions posed here:

https://www.postgresql.org/message-id/2184af82-8dbd-4c78-9cc1-29f7a577e2f1%40aklaver.com
> 
> 
> Thank you
> Johnathan Tiamoh

-- 
Adrian Klaver
adrian.klaver@aklaver.com






^ permalink  raw  reply  [nested|flat] 24+ messages in thread


end of thread, other threads:[~2023-12-26 20:58 UTC | newest]

Thread overview: 24+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2004-07-07 21:05 ERROR: missing chunk number 0 for toast value 14227980 Diogo Biazus <diogob@gmail.com>
2004-07-07 21:40 ` Chris Smith <cdsmith@twu.net>
2011-02-28 00:25 ERROR:  missing chunk number 0 for toast value 382548694 in pg_toast_847386 Michael Harris <michael.harris@ericsson.com>
2011-02-28 04:06 ` Re: ERROR: missing chunk number 0 for toast value 382548694 in pg_toast_847386 Vibhor Kumar <vibhor.kumar@enterprisedb.com>
2011-02-28 04:16   ` Re: ERROR:  missing chunk number 0 for toast value 382548694 in pg_toast_847386 Michael Harris <michael.harris@ericsson.com>
2011-02-28 04:24     ` Re: ERROR: missing chunk number 0 for toast value 382548694 in pg_toast_847386 Vibhor Kumar <vibhor.kumar@enterprisedb.com>
2011-02-28 04:43       ` Re: ERROR:  missing chunk number 0 for toast value 382548694 in pg_toast_847386 Michael Harris <michael.harris@ericsson.com>
2011-02-28 05:57         ` Re: ERROR: missing chunk number 0 for toast value 382548694 in pg_toast_847386 Vibhor Kumar <vibhor.kumar@enterprisedb.com>
2011-02-28 06:27           ` Re: ERROR:  missing chunk number 0 for toast value 382548694 in pg_toast_847386 Michael Harris <michael.harris@ericsson.com>
2015-05-28 01:28 ERROR: missing chunk number 0 for toast value 1821556134 in pg_toast_17881 Tory M Blue <tmblue@gmail.com>
2016-06-23 06:38 ERROR:  missing chunk number 0 for toast value while using logical decoder.\ sudalai <sudalait2@gmail.com>
2016-06-23 06:53 ` Re: ERROR: missing chunk number 0 for toast value while using logical decoder.\ John R Pierce <pierce@hogranch.com>
2016-06-23 07:20   ` Re: ERROR: missing chunk number 0 for toast value while using logical decoder.\ sudalai <sudalait2@gmail.com>
2016-06-23 07:20 ` Re: ERROR: missing chunk number 0 for toast value while using logical decoder.\ Michael Paquier <michael.paquier@gmail.com>
2016-06-23 07:55   ` Re: ERROR: missing chunk number 0 for toast value while using logical decoder.\ sudalai <sudalait2@gmail.com>
2016-06-23 08:03     ` Re: Re: ERROR: missing chunk number 0 for toast value while using logical decoder.\ Michael Paquier <michael.paquier@gmail.com>
2016-06-23 12:09       ` Re: ERROR: missing chunk number 0 for toast value while using logical decoder.\ sudalai <sudalait2@gmail.com>
2016-07-18 07:31       ` Re: ERROR: missing chunk number 0 for toast value while using logical decoder.\ sudalai <sudalait2@gmail.com>
2016-07-18 09:09         ` Re: Re: ERROR: missing chunk number 0 for toast value while using logical decoder.\ Michael Paquier <michael.paquier@gmail.com>
2016-07-18 10:08           ` Re: ERROR: missing chunk number 0 for toast value while using logical decoder.\ sudalai <sudalait2@gmail.com>
2016-07-18 10:55             ` Re: Re: ERROR: missing chunk number 0 for toast value while using logical decoder.\ Michael Paquier <michael.paquier@gmail.com>
2016-07-18 11:32               ` Re: ERROR: missing chunk number 0 for toast value while using logical decoder.\ sudalai <sudalait2@gmail.com>
2023-12-26 20:51 ERROR:  missing chunk number 0 for toast value 1563962066 in pg_toast_2619 Johnathan Tiamoh <johnathantiamoh@gmail.com>
2023-12-26 20:58 ` Re: ERROR: missing chunk number 0 for toast value 1563962066 in pg_toast_2619 Adrian Klaver <adrian.klaver@aklaver.com>

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox