| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Steven Flatt" <steven(dot)flatt(at)gmail(dot)com> |
| Cc: | pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: Foreign Key Deadlocking |
| Date: | 2007-04-18 17:47:37 |
| Message-ID: | 5757.1176918457@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
"Steven Flatt" <steven(dot)flatt(at)gmail(dot)com> writes:
> Hi, we're using Postgres 8.1.4.
> We've been seeing deadlock errors of this form, sometimes as often as
> several times per hour:
> ...
> I also see claims that this problem is fixed in 8.2, and if the fix is what
> I think it is, it's also in 8.1.6.
> Can someone confirm that I've identified the right fix?
Hard to say without a lot more data, but as a general rule you should be
on 8.1.latest in any case. See
http://www.postgresql.org/support/versioning
You might also find ammunition in the release notes:
http://developer.postgresql.org/pgdocs/postgres/release.html
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jim C. Nasby | 2007-04-18 18:07:59 | Re: a question about Direct I/O and double buffering |
| Previous Message | Jim C. Nasby | 2007-04-18 17:19:59 | Re: Shared buffers, db transactions commited, and write IO on Solaris |