From: Tom Lane <tgl@sss.pgh.pa.us>
To: Carlos Moreno <moreno@mochima.com>
To: PgSQL Performance ML <pgsql-performance@postgresql.org>
Subject: Re: Having trouble with backups (was: Re: Crash Recovery)
Date: Fri, 24 Jan 2003 20:29:41 -0500
Message-ID: <28260.1043458181@sss.pgh.pa.us> (raw)
In-Reply-To: <28204.1043457542@sss.pgh.pa.us>
References: <2147483647.1043361178@[10.0.1.133]>
<1043416377.29437.70.camel@haggis>
<3E3158DA.7080807@mochima.com>
<22650.1043442101@sss.pgh.pa.us>
<3E31DA80.7000000@mochima.com>
<28204.1043457542@sss.pgh.pa.us>
I said:
> Carlos Moreno <moreno@mochima.com> writes:
>> One quick question, Tom, before some general comments and
>> reply to the other messages... Where would I specify any
>> locks the software wants to do?
> If you are not issuing any explicit "LOCK" SQL commands, then you can
> disregard my theory.
Actually, that's too simple. Are you creating and dropping tables,
or issuing schema-change commands (such as ADD COLUMN or RENAME)?
All of those things take exclusive locks on the tables they modify.
Ordinary SELECT/INSERT/UPDATE/DELETE operations can run in parallel with
pg_dump, but messing with the database structure is another story.
I guess the real question here is whether your app is actually stopped
dead (as it would be if waiting for a lock), or just slowed to a crawl
(as a performance problem could do). I cannot tell if your "frozen"
description is hyperbole or literal truth.
One thing that might help diagnose it is to look at the output of ps
auxww (or ps -ef on SysV-ish platforms) to see what all the backends are
currently doing while the problem exists.
regards, tom lane
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-performance@postgresql.org
Cc: tgl@sss.pgh.pa.us, moreno@mochima.com
Subject: Re: Having trouble with backups (was: Re: Crash Recovery)
In-Reply-To: <28260.1043458181@sss.pgh.pa.us>
References: <2147483647.1043361178@[10.0.1.133]> <1043416377.29437.70.camel@haggis> <3E3158DA.7080807@mochima.com> <22650.1043442101@sss.pgh.pa.us> <3E31DA80.7000000@mochima.com> <28204.1043457542@sss.pgh.pa.us> <28260.1043458181@sss.pgh.pa.us>
* 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