Re: can you have any idea about toast missing chunk issu resolution
От
M Tarkeshwar Rao
Тема
Re: can you have any idea about toast missing chunk issu
resolution
Дата
Msg-id
1C16813DAFF3E44B939586605D40E9F011769320@ESESSMB107.ericsson.se
Ответ на
Список
Дерево обсуждения
can you have any idea about toast missing chunk issu resolution M Tarkeshwar Rao <m.tarkeshwar.rao@ericsson.com>
Re: can you have any idea about toast missing chunk issu resolution Tom Lane <tgl@sss.pgh.pa.us>
Re: can you have any idea about toast missing chunk issu
resolution M Tarkeshwar Rao <m.tarkeshwar.rao@ericsson.com>
Re: can you have any idea about toast missing chunk issu resolution Michael Paquier <michael.paquier@gmail.com>
Re: can you have any idea about toast missing chunk issu
resolution Adrian Klaver <adrian.klaver@aklaver.com>
Re: can you have any idea about toast missing chunk issu resolution Thomas Kellerer <spam_eater@gmx.net>
Thanks Tom for your quick reply. We are using 9.1.3. We got some information on internet regarding this and also found bug IDs: You have any idea is these bugs are fixed in any release or fixed in latest 9.3.5? We are in blocking stage as many users depend on this. Can you please help us in resolution? BUG #9187: corrupt toast tables http://www.postgresql.org/message-id/30154.1392ds 153590@sss.pgh.pa.us http://www.postgresql.org/message-id/CAFj8pRAufPtTn5+ohFqPbcd1JzkErsCK51UAkHCWd8nt4osXjA@mail.gmail.com http://www.postgresql.org/message-id/20140211162408.2713.81446@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 Regards Tarkeshwar -----Original Message----- From: Tom Lane [mailto:tgl@sss.pgh.pa.us] Sent: 15 January 2015 20:16 To: M Tarkeshwar Rao Cc: pgsql-general@postgresql.org Subject: Re: [GENERAL] can you have any idea about toast missing chunk issu resolution M Tarkeshwar Rao writes: > ERROR: missing chunk number 0 for toast value 54787 in pg_toast_2619 What PG version is that exactly? If you're not running the latest minor release in your branch, updating would be advisable; there have been fixes in the past for bugs with symptoms like this. If you still see the issue after updating, an ANALYZE on the problem table would probably help. regards, tom lane
В списке pgsql-general по дате отправления