Re: FATAL: lock AccessShareLock on object 0/1260/0 is already held
В списке pgsql-hackers по дате отправления:
| От | Tom Lane |
|---|---|
| Тема | Re: FATAL: lock AccessShareLock on object 0/1260/0 is already held |
| Дата | |
| Msg-id | 23117.1315495911@sss.pgh.pa.us обсуждение |
| Ответ на | Re: FATAL: lock AccessShareLock on object 0/1260/0 is already held (daveg <daveg@sonic.net>) |
| Список | pgsql-hackers |
daveg <daveg@sonic.net> writes:
> On Wed, Sep 07, 2011 at 09:02:04PM -0400, Tom Lane wrote:
>> daveg <daveg@sonic.net> writes:
>>> The first version we saw it on was 8.4.7.
>> Yeah, you said that. I was wondering what you'd last run before 8.4.7.
> Sorry, misunderstood. We were previously running 8.4.4, but have been on 8.4.7
> since shortly after it was released. Prior to that we have had all the major
> and most of the minor releases since 7.1.
Well, I groveled through the commit logs from 8.4.4 to 8.4.7, and
I can't find anything that looks like it could possibly be related.
So at this point I'm inclined to think that the bug is older than
that, but your usage patterns changed so that you started to tickle it.
Can you think of any changes in your usage that might date to around
that time, and would somehow be connected to backend startup/shutdown?
regards, tom lane
В списке pgsql-hackers по дате отправления:
Сайт использует файлы cookie для корректной работы и повышения удобства. Нажимая кнопку «Принять» или продолжая пользоваться сайтом, вы соглашаетесь на их использование в соответствии с Политикой в отношении обработки cookie ООО «ППГ», в том числе на передачу данных из файлов cookie сторонним статистическим и рекламным службам. Вы можете управлять настройками cookie через параметры вашего браузера