Thank you both, this clears everything up for me.
Cheers,
Mike
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
On Thu, Dec 20, 2007 at 12:55:02AM -0500, Tom Lane wrote:
> "Mike C" <[EMAIL PROTECTED]> 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 no
[ Pavan already answered most of this, but ... ]
"Mike C" <[EMAIL PROTECTED]> 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
On Dec 20, 2007 3:44 AM, Mike C <[EMAIL PROTECTED]> wrote:
> Hi,
>
> Can someone clarify HOT updates for me (and perhaps put more detail
> into the docs?). Is this statement correct: the HOT technique is used
> on *any* table so long as no indexed column is affected.
>
Its partially correct. HOT
Hi,
Can someone clarify HOT updates for me (and perhaps put more detail
into the docs?). Is this statement correct: the HOT technique is used
on *any* table so long as no indexed column is affected.
create table T (A int, B int);
create index TB on T (B);
insert into T (A,B) Values (1,2);
So if
