Re: Read-only transactions - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Read-only transactions
Date
Msg-id 8186.1041898522@sss.pgh.pa.us
Whole thread Raw
In response to Read-only transactions  (Peter Eisentraut <peter_e@gmx.net>)
Responses Re: Read-only transactions  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-hackers
Peter Eisentraut <peter_e@gmx.net> writes:
> I would like to implement read-only transactions following the SQL spec,
> ...
> I think it's light-weight and marginally useful.

"Light-weight" would depend on your intended implementation, I suppose.
Where are you planning to check this?

Also, the fact that you are excluding temp tables seems to suggest that
this is a very high-level, abstract notion of read-only-ness; it's
certainly got little to do with whether we try to write on the disk.
As such it's not clear to me why vacuum and checkpoint are included in
the forbidden list.  They don't logically change any data.  The same
might be said of reindex.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Read-only transactions
Next
From: "Dann Corbit"
Date:
Subject: I feel the need for speed. What am I doing wrong?