| From: | David Fetter <david(at)fetter(dot)org> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | pgsql-general(at)postgresql(dot)org, "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
| Subject: | Re: BEGIN WORK READ ONLY; |
| Date: | 2006-10-16 05:42:18 |
| Message-ID: | 20061016054218.GH822@fetter.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Sun, Oct 15, 2006 at 11:39:20AM +0200, Peter Eisentraut wrote:
> David Fetter wrote:
> > It would be handy for things like pgpool and Continuent, which
> > could reliably distinguish up front the difference between a
> > transaction that can write and one that can safely be sliced up
> > and dispatched to read-only databases.
>
> Yes, I think that would be the use case. I wish someone were to
> implement that.
I think you meant "would" rather than "were to." ;)
I've brought it up with the pgpool people :)
Cheers,
D
--
David Fetter <david(at)fetter(dot)org> http://fetter.org/
phone: +1 415 235 3778 AIM: dfetter666
Skype: davidfetter
Remember to vote!
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rafal Pietrak | 2006-10-16 06:13:38 | Re: Data visibility |
| Previous Message | Richard Broersma Jr | 2006-10-16 04:43:10 | techdocs.2 how long has this be around? |