From: | Allan Kamau <kamauallan(at)gmail(dot)com> |
---|---|
To: | Postgres General Postgres General <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Deadlocks On Demand |
Date: | 2010-01-03 16:18:52 |
Message-ID: | ab1ea6541001030818o6aac169ej7cba58b2c54a4b9b@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Sun, Jan 3, 2010 at 5:43 AM, David Fetter <david(at)fetter(dot)org> wrote:
> Folks,
>
> I'm working on some SQL intended to expose lock conditions (deadlock,
> etc.), but to do this, I need to be able to create such conditions at
> will. Rather than build an entire infrastructure from scratch, I'd
> like to know if there are any frameworks people are using to create
> such conditions, and if so, what they are.
>
> One possibility I've come up with is to finish up the concurrent psql
> proposal that's been floating around for some time.
>
> http://archives.postgresql.org/pgsql-patches/2007-05/msg00112.php
>
> What say?
>
> Cheers,
> David.
> --
> David Fetter <david(at)fetter(dot)org> http://fetter.org/
> Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter
> Skype: davidfetter XMPP: david(dot)fetter(at)gmail(dot)com
> iCal: webcal://www.tripit.com/feed/ical/people/david74/tripit.ics
>
> Remember to vote!
> Consider donating to Postgres: http://www.postgresql.org/about/donate
>
> --
> Sent via pgsql-general mailing list (pgsql-general(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general
>
I am trying to come up with a probable use case scenario for such
implementation.
From | Date | Subject | |
---|---|---|---|
Next Message | David Fetter | 2010-01-03 18:02:39 | Re: set-level update fails with unique constraint violation |
Previous Message | Emanuel Calvo Franco | 2010-01-03 12:44:54 | Re: Innotop for postgresl |