| From: | Karsten Hilbert <Karsten(dot)Hilbert(at)gmx(dot)net> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Postgres 8.3 HOT and non-persistent xids |
| Date: | 2007-12-20 11:05:54 |
| Message-ID: | 20071220110554.GB5701@merkur.hilbert.loc |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Thu, Dec 20, 2007 at 12:55:02AM -0500, Tom Lane wrote:
> "Mike C" <smith(dot)not(dot)western(at)gmail(dot)com> writes:
> > And for non-persistent transaction ids, the documentation says that
> > this is for read-only transactions. What defines a read-only
> > transaction for this purpose?
>
> A transaction that has not done anything that requires it to sign an
> update with its transaction ID.
In this context, when I set a connection to READ ONLY do any
transactions run on the connection ever bother to do any of
the transactional-writes housekeeping (such as txid
signing) ?
Karsten
--
GPG key ID E4071346 @ wwwkeys.pgp.net
E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Richard Huxton | 2007-12-20 11:14:07 | Re: Quick Regex Question |
| Previous Message | Martijn van Oosterhout | 2007-12-20 11:03:57 | Re: Quick Regex Question |