From: Kevin Brown <kevin@sysexperts.com>
To: PgSQL Performance ML <pgsql-performance@postgresql.org>
Subject: Re: Having trouble with backups (was: Re: Crash Recovery)
Date: Fri, 24 Jan 2003 17:04:36 -0800
Message-ID: <20030125010436.GB28252@filer> (raw)
In-Reply-To: <3E31DA80.7000000@mochima.com>
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>
Carlos Moreno wrote:
> And no, as I said above, I don't think the software locks
> any tables -- in fact, if you ask me, I would say *there
> is* bad coding in the application, but precisely because
> there are no locks, no transactions (I know, shame on me!
> That's near the top in the list of most important things
> to do...), so that's why I was so reluctant to believe
> my colleague when he insisted that the pg_dump's were
> "freezing" the application... I had to see it with my
> own eyes, and on two different occasions, to be convinced
> :-(
>
> In case this tells you something... The size of the
> backup files (in plain ASCII) are around 300MB (the
> command is "nice pg_dump -c -f file.sql dbname").
One thing you can do to help track this down is to place
stats_command_string = on
in your postgresql.conf and restart the database (it may be sufficient
to tell the database to reread the config file via "pg_ctl reload").
Then, when the backup is going, run the application.
When it "freezes", connect to the database via psql as the user
postgres and do a "select * from pg_stat_activity". You'll see the
list of connected processes and the current query being executed by
each, if any.
Do that multiple times and you should see the progress, if any, the
application is making in terms of database queries.
Hope this helps...
--
Kevin Brown kevin@sysexperts.com
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: kevin@sysexperts.com
Subject: Re: Having trouble with backups (was: Re: Crash Recovery)
In-Reply-To: <20030125010436.GB28252@filer>
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> <20030125010436.GB28252@filer>
* 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