| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | JC Praud <brutaltruth42(at)gmail(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: auto truncate/vacuum full |
| Date: | 2009-10-28 15:36:07 |
| Message-ID: | 20091028153607.GJ5018@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
JC Praud escribió:
> On Wed, Oct 28, 2009 at 12:29 AM, Alvaro Herrera <alvherre(at)commandprompt(dot)com
> > This bit does not make much sense to me. A transaction waiting will not
> > show up in the log. Were they cancelled? Can you paste an extract from
> > the log?
>
> No, the transactions were not cancelled. All I saw in he pg_log is this
> (taken at the time le lock was lifted):
>
> 2009-10-27 05:39:19 CET dbuser dbase 10.33.10.133 LOG: process 14866 still
> waiting for RowExclusiveLock on relation 26683 of database 23806 after
> 5000.271 ms
Oh, you have log_lock_waits enabled. It makes plenty of sense now,
thanks.
--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sam Mason | 2009-10-28 15:36:48 | Re: could not find array type for data type character varying[] |
| Previous Message | Tom Lane | 2009-10-28 15:30:41 | Re: could not find array type for data type character varying[] |