| From: | "Brian A(dot) Seklecki" <lavalamp(at)spiritual-machines(dot)org> |
|---|---|
| To: | Stephane Bailliez <sbailliez(at)gmail(dot)com> |
| Cc: | pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: Frequent pg_clog on system |
| Date: | 2007-05-18 14:40:48 |
| Message-ID: | 1179499248.41472.212.camel@soundwave.pgh.priv.collaborativefusion.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Anything in /var/log/messages at this time? Try turning up the
debugging for transaction logging?
~BAS
On Fri, 2007-05-18 at 12:08 +0200, Stephane Bailliez wrote:
> n after a sql query performs a long scan of table A or B.
> That's very weird since each time it seems to happen after performing
> more or less the same query several times (trial and error narrowing
> them data) and suddenly I have this error happening and I'm cooked
> (fwiw, there is no insert/update happening at all during this period,
> only select and a single user)
>
> Anyone has any idea what could be the cause of this ? It's a bit too
> recurrent to me and it's a definite annoyance.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2007-05-18 15:10:21 | Re: ERROR: invalid memory alloc request size |
| Previous Message | Joshua D. Drake | 2007-05-18 14:24:19 | Re: cross database references... |