From: sudalai <sudalait2@gmail.com>
To: pgsql-general@postgresql.org
Subject: Re: ERROR: missing chunk number 0 for toast value while using logical decoder.\
Date: Mon, 18 Jul 2016 00:31:53 -0700 (MST)
Message-ID: <1468827113922-5912389.post@n5.nabble.com> (raw)
In-Reply-To: <CAB7nPqTAd9npn_iw3VZRZQ5oL8r6L=zuM-FhoE7=R60k3vPXVw@mail.gmail.com>
References: <1466663905344-5909194.post@n5.nabble.com>
<CAB7nPqSAKEtTsME_d+eMh0WXWXT=k02nhy7oDrYNSmTnun=gqQ@mail.gmail.com>
<1466668548595-5909207.post@n5.nabble.com>
<CAB7nPqTAd9npn_iw3VZRZQ5oL8r6L=zuM-FhoE7=R60k3vPXVw@mail.gmail.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-general@postgresql.org
Cc: sudalait2@gmail.com
Subject: Re: ERROR: missing chunk number 0 for toast value while using logical decoder.\
In-Reply-To: <1468827113922-5912389.post@n5.nabble.com>
References: <1466663905344-5909194.post@n5.nabble.com> <CAB7nPqSAKEtTsME_d+eMh0WXWXT=k02nhy7oDrYNSmTnun=gqQ@mail.gmail.com> <1466668548595-5909207.post@n5.nabble.com> <CAB7nPqTAd9npn_iw3VZRZQ5oL8r6L=zuM-FhoE7=R60k3vPXVw@mail.gmail.com> <1468827113922-5912389.post@n5.nabble.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
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