On Thu, 2010-06-03 at 13:11 -0500, Kevin Grittner wrote:
> Based on what I've heard so far, I wouldn't entirely
>
> rule out some sort of bloat being a factor, either.
>
> -Kevin
Index/table bloat is the first thing I suspected, and both table and
indices look all the right size. Knowing how
Claudio Freire wrote:
> On Thu, 2010-06-03 at 13:42 -0400, Tom Lane wrote:
>> Claudio Freire writes:
>> > What I did do is analyze server load during the events, and as
>> > I suspected, disk activity during the "deadlocks" seems to
>> > suggest a vacuuming taking place. Although there was no
>>
On Thu, 2010-06-03 at 13:42 -0400, Tom Lane wrote:
> Claudio Freire writes:
> > What I did do is analyze server load during the events, and as I
> > suspected, disk activity during the "deadlocks" seems to suggest a
> > vacuuming taking place. Although there was no autovacuum entry in
> > pg_stat
On Fri, 2010-04-30 at 11:50 -0400, Tom Lane wrote:
> "Kevin Grittner" writes:
> > Eliminating null columns and mangling column headers for length, I
> > get this:
>
> > locktype| tranid | virtualx | pid | mode | gr
> > transactionid | 39773877 | 63/15761 | 11157 | ShareLock
Claudio Freire writes:
> What I did do is analyze server load during the events, and as I
> suspected, disk activity during the "deadlocks" seems to suggest a
> vacuuming taking place. Although there was no autovacuum entry in
> pg_stat_activity every time I checked, disk activity precisely matche
On Fri, 2010-04-30 at 12:32 -0400, Tom Lane wrote:
> "Kevin Grittner" writes:
> > Claudio Freire wrote:
> >> I know it doesn't look like a deadlock from where you're standing,
> >> but it does so from where I am.
>
> > It's possible that you're filtering out the information which would
> > be
On Fri, 2010-04-30 at 11:14 -0500, Kevin Grittner wrote:
> Claudio Freire wrote:
>
> > I know it doesn't look like a deadlock from where you're standing,
> > but it does so from where I am.
>
> It's possible that you're filtering out the information which would
> be most useful to diagnosing
On Fri, 2010-04-30 at 11:50 -0400, Tom Lane wrote:
> "Kevin Grittner" writes:
> > Eliminating null columns and mangling column headers for length, I
> > get this:
>
> > locktype| tranid | virtualx | pid | mode | gr
> > transactionid | 39773877 | 63/15761 | 11157 | ShareLock
"Kevin Grittner" writes:
> Claudio Freire wrote:
>> I know it doesn't look like a deadlock from where you're standing,
>> but it does so from where I am.
> It's possible that you're filtering out the information which would
> be most useful to diagnosing the problem. Next time it happens,
> pl
Claudio Freire wrote:
> I know it doesn't look like a deadlock from where you're standing,
> but it does so from where I am.
It's possible that you're filtering out the information which would
be most useful to diagnosing the problem. Next time it happens,
please send the entire output from p
"Kevin Grittner" writes:
> Eliminating null columns and mangling column headers for length, I
> get this:
> locktype| tranid | virtualx | pid | mode | gr
> transactionid | 39773877 | 63/15761 | 11157 | ShareLock | f
> transactionid | 39773877 | 4/10902 | 6421 | ExclusiveLo
On Fri, 2010-04-30 at 08:47 -0500, Kevin Grittner wrote:
> Peter Eisentraut wrote:
>
> > This is not a deadlock.
>
> Agreed.
>
> > It's just two locks on the same table
>
> Not as I read it.
>
> > (and maybe a bit more readable formatting).
>
> Eliminating null columns and mangling co
Peter Eisentraut wrote:
> This is not a deadlock.
Agreed.
> It's just two locks on the same table
Not as I read it.
> (and maybe a bit more readable formatting).
Eliminating null columns and mangling column headers for length, I
get this:
>> locktype| tranid | virtualx | pid
On fre, 2010-04-30 at 03:51 +, Claudio wrote:
> The following bug has been logged online:
>
> Bug reference: 5443
> Logged by: Claudio
> Email address: clau...@livra.com
> PostgreSQL version: 8.3.7
> Operating system: CentOS
> Description:Undetected deadlock situat
The following bug has been logged online:
Bug reference: 5443
Logged by: Claudio
Email address: clau...@livra.com
PostgreSQL version: 8.3.7
Operating system: CentOS
Description:Undetected deadlock situation
Details:
During a massive update of a table A, a single-row
15 matches
Mail list logo
