From: | <me(at)alternize(dot)com> |
---|---|
To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | <pgsql-novice(at)postgresql(dot)org> |
Subject: | Re: speeding up pg_dump? |
Date: | 2005-12-27 05:39:44 |
Message-ID: | 006a01c60aa7$f13d2410$6402a8c0@iwing |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-novice |
> Me either. Do you have operations that are taking exclusive locks on
> tables?
there is one exclusive lock...
locktype | database | relation | page | tuple | transactionid |
classid | objid | objsubid | transaction | pid | mode | granted
---------------+----------+----------+------+-------+---------------+---------+-------+----------+-------------+------+-----------------+---------
relation | 4131529 | 10342 | | | |
| | | 42571885 | 3680 | AccessShareLock | t
transactionid | | | | | 42571885 |
| | | 42571885 | 3680 | ExclusiveLock | t
(2 rows)
but this lock is also present when restarting the db, so i guess this
shouldn't hurt?
VACUUM FULL takes around 15min...
- thomas
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2005-12-27 05:56:05 | Re: speeding up pg_dump? |
Previous Message | Tom Lane | 2005-12-27 04:35:18 | Re: speeding up pg_dump? |