| From: | John R Pierce <pierce(at)hogranch(dot)com> |
|---|---|
| To: | David Fetter <david(at)fetter(dot)org> |
| Cc: | PostgreSQL <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: deadlock |
| Date: | 2010-08-12 05:39:01 |
| Message-ID: | 4C6388F5.8000904@hogranch.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 08/11/10 6:32 PM, David Fetter wrote:
>> does anyone have any suggestions for what to look for, or what sort
>> of common partition management mistakes in the application could
>> lead to this sort of deadlock?
> DDL is a "don't do it at peak load" event. More realistically, it's
> more like a "down time" event. Maybe when we have "real"
> partitioning...
Thats an *ouch* for this application, as the load is a 24/7 thing... the
database has to handle a steady stream of events and requests at a
fairly high rate coming from a factory operation, and we need to prune
weekly partitions while all the rest is going on.
The developers (and operations) are coming from an Oracle Enterprise
environment, where this all just works. I've been pushing for years to
give postgres a try, this is the first substantial database deployment.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Smith | 2010-08-12 05:41:06 | Re: MySQL versus Postgres |
| Previous Message | Sandeep Srinivasa | 2010-08-12 05:35:55 | Re: MySQL versus Postgres |