On Mon, Jul 18, 2016 at 4:31 PM, sudalai <sudalait2(at)gmail(dot)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