Re: Summary and Plan for Hot Standby

From: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>
To: Tatsuo Ishii <ishii(at)sraoss(dot)co(dot)jp>
Cc: simon(at)2ndQuadrant(dot)com, ishii(at)postgresql(dot)org, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Summary and Plan for Hot Standby
Date: 2009-11-19 08:59:33
Message-ID: 4B0508F5.9030803@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tatsuo Ishii wrote:
> Sorry for confusion. My example is under normal PostgreSQL, not under
> HS enabled.

You get the same result in standby:

postgres=# begin;
BEGIN
postgres=# prepare a(int) as insert into foo values($1);
PREPARE
postgres=# SELECT * FROM pg_locks;
locktype │ database │ relation │ page │ tuple │ virtualxid │
transactionid │
classid │ objid │ objsubid │ virtualtransaction │ pid │ mode
│ gra
nted
────────────┼──────────┼──────────┼──────┼───────┼────────────┼───────────────┼─
────────┼───────┼──────────┼────────────────────┼───────┼──────────────────┼────
─────
relation │ 11564 │ 10968 │ │ │ │

│ │ │ 2/4 │ 10449 │
AccessShareLock │ t
relation │ 11564 │ 16384 │ │ │ │

│ │ │ 2/4 │ 10449 │
RowExclusiveLock │ t
virtualxid │ │ │ │ │ 1/1 │

│ │ │ 1/0 │ 10419 │ ExclusiveLock
│ t
virtualxid │ │ │ │ │ 2/4 │

│ │ │ 2/4 │ 10449 │ ExclusiveLock
│ t
(4 rows)

this is from a standby.

--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Simon Riggs 2009-11-19 09:00:05 Re: Summary and Plan for Hot Standby
Previous Message Simon Riggs 2009-11-19 08:58:28 Re: Summary and Plan for Hot Standby