Re: [GENERAL] BEGIN WORK READ ONLY;

2006-10-15 Thread David Fetter
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 dis

Re: [GENERAL] BEGIN WORK READ ONLY;

2006-10-15 Thread Peter Eisentraut
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

Re: [GENERAL] BEGIN WORK READ ONLY;

2006-10-14 Thread Ron Johnson
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 10/14/06 14:35, Michael Fuhr wrote: > On Sat, Oct 14, 2006 at 11:35:12AM -0700, Joshua D. Drake wrote: >> What is the use case for a READ ONLY transaction? > > I use read-only transactions as a safety net for interactive sessions > when I want to a

Re: [GENERAL] BEGIN WORK READ ONLY;

2006-10-14 Thread A. Kretschmer
am Sat, dem 14.10.2006, um 13:35:21 -0600 mailte Michael Fuhr folgendes: > On Sat, Oct 14, 2006 at 11:35:12AM -0700, Joshua D. Drake wrote: > > What is the use case for a READ ONLY transaction? > > I use read-only transactions as a safety net for interactive sessions > when I want to avoid modify

Re: [GENERAL] BEGIN WORK READ ONLY;

2006-10-14 Thread Michael Fuhr
On Sat, Oct 14, 2006 at 03:42:48PM -0400, Tom Lane wrote: > David Fetter <[EMAIL PROTECTED]> writes: > > On Sat, Oct 14, 2006 at 11:35:12AM -0700, Joshua D. Drake wrote: > >> What is the use case for a READ ONLY transaction? > > > It would be handy for things like pgpool and Continuent, which coul

Re: [GENERAL] BEGIN WORK READ ONLY;

2006-10-14 Thread Tom Lane
David Fetter <[EMAIL PROTECTED]> writes: > On Sat, Oct 14, 2006 at 11:35:12AM -0700, Joshua D. Drake wrote: >> What is the use case for a READ ONLY transaction? > It would be handy for things like pgpool and Continuent, which could > reliably distinguish up front the difference between a transacti

Re: [GENERAL] BEGIN WORK READ ONLY;

2006-10-14 Thread Michael Fuhr
On Sat, Oct 14, 2006 at 11:35:12AM -0700, Joshua D. Drake wrote: > What is the use case for a READ ONLY transaction? I use read-only transactions as a safety net for interactive sessions when I want to avoid modifying anything accidentally. Here's an example: CREATE ROLE foo LOGIN PASSWORD 'pass

Re: [GENERAL] BEGIN WORK READ ONLY;

2006-10-14 Thread David Fetter
On Sat, Oct 14, 2006 at 11:35:12AM -0700, Joshua D. Drake wrote: > Hello, > > Command Prompt has been teaching alot of classes lately, and one of the > questions that I received recently was: > > What is the use case for a READ ONLY transaction? It would be handy for things like pgpool and Conti

Re: [GENERAL] BEGIN WORK READ ONLY;

2006-10-14 Thread Joshua D. Drake
Tom Lane wrote: > "Joshua D. Drake" <[EMAIL PROTECTED]> writes: >> What is the use case for a READ ONLY transaction? > >> I haven't been able to come up with a good answer. Anyone got a use case >> for this feature? I know the community didn't implement it for giggles. > > No, we implemented it b

Re: [GENERAL] BEGIN WORK READ ONLY;

2006-10-14 Thread Tom Lane
"Joshua D. Drake" <[EMAIL PROTECTED]> writes: > What is the use case for a READ ONLY transaction? > I haven't been able to come up with a good answer. Anyone got a use case > for this feature? I know the community didn't implement it for giggles. No, we implemented it because it's required by the