From: Marc G. Fournier <scrappy@postgresql.org>
To: Matt Clark <matt@ymogen.net>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-admin@postgresql.org
Subject: Re: Frequent 'deadlock detected' in 7.4 ... or just my bad
Date: Mon, 5 Apr 2004 18:39:08 -0300 (ADT)
Message-ID: <20040405183841.N57651@ganymede.hub.org> (raw)
In-Reply-To: <OAEAKHEHCMLBLIDGAFELCENEFDAA.matt@ymogen.net>
References: <OAEAKHEHCMLBLIDGAFELCENEFDAA.matt@ymogen.net>
That appears to have fixed it, thanks ... at least it hasn't happened in a
few hours, and it was happening at least once an hour previously ...
On Mon, 5 Apr 2004, Matt Clark wrote:
> > 1. a traffic table is read in, and loaded into a hash table that is
> > ordered by company_id, ip_id and port:
> >
> > $traffic{$ip_rec{$ip}{'company_id'}}{$ip_id}{$port} += $bytes1 + $bytes2;
> >
> > 2. a foreach loop is run on that resultant list to do the updates to the
> > database:
> >
> > foreach $company_id ( keys %traffic ) {
> > foreach $ip_id ( keys %{$traffic{$company_id}} ) {
> > foreach $port ( keys %{$traffic{$company_id}{$ip_id}} ) {
> >
> > and the updates are done based on those 3 values, plus the byte value
> > of $traffic{$company_id}{$ip_id}{$port} ...
> >
> > Now, my first mistake may be that I'm mis-assuming that the hashes will
> > be read in a sorted order ... ? If this is the case, though, then sort
> > order shouldn't be an issue, as all servers would be sorted the same way
>
> The output of keys(%hash) is NOT ordered! Try:
>
> foreach $company_id ( sort keys %traffic ) {
> foreach $ip_id ( sort keys %{$traffic{$company_id}} ) {
> foreach $port ( sort keys %{$traffic{$company_id}{$ip_id}} ) {
>
>
> Matt
>
>
----
Marc G. Fournier Hub.Org Networking Services (http://www.hub.org)
Email: scrappy@hub.org Yahoo!: yscrappy ICQ: 7615664
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-admin@postgresql.org
Cc: scrappy@postgresql.org, matt@ymogen.net, tgl@sss.pgh.pa.us
Subject: Re: Frequent 'deadlock detected' in 7.4 ... or just my bad
In-Reply-To: <20040405183841.N57651@ganymede.hub.org>
References: <OAEAKHEHCMLBLIDGAFELCENEFDAA.matt@ymogen.net> <20040405183841.N57651@ganymede.hub.org>
* 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