From: Josh Berkus <josh@agliodbs.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
To: Josh Berkus <josh@agliodbs.com>
Cc: pgsql-sql@postgresql.org
Subject: Re: Function won't complete
Date: Sun, 28 Apr 2002 12:39:06 -0700
Message-ID: <web-1387143@davinci.ethosmedia.com> (raw)
In-Reply-To: <7079.1019943371@sss.pgh.pa.us>
Tom,
> This analysis is nonsense, because PG does not rely on WAL for
> transaction rollback, and the amount of WAL activity is *not*
> proportional to transaction length. (At least not since 7.1.2.)
<snip>
> However, until you drop
> your focus on the WAL we'll not find out what's really the
> bottleneck...
Sorry, Tom. I was used to the problems of 7.1.2, and didn't really
"get it" when you told me things had changed.
I still say it's the disk I/O, and I think your explanation of dead
tuples makes a lot of sense. The debug log is full of this:
DEBUG: proc_exit(0)
DEBUG: shmem_exit(0)
DEBUG: exit(0)
DEBUG: reaping dead processes
DEBUG: child process (pid 11933) exited with exit code 0
DEBUG: proc_exit(0)
DEBUG: shmem_exit(0)
DEBUG: exit(0)
DEBUG: reaping dead processes
DEBUG: child process (pid 11939) exited with exit code 0
And each one of the cycles about takes 5-10 minutes.
I'm a little reluctant to dump everything to the list, as we're talking
about a lot of data and code. Lemme do some judicious editing and I'll
send you a gzip package this week.
-Josh Berkus
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 using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: josh@agliodbs.com, tgl@sss.pgh.pa.us
Subject: Re: Function won't complete
In-Reply-To: <web-1387143@davinci.ethosmedia.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