Re: Summary and Plan for Hot Standby - Mailing list pgsql-hackers

From Heikki Linnakangas
Subject Re: Summary and Plan for Hot Standby
Date
Msg-id 4B0508F5.9030803@enterprisedb.com
Whole thread Raw
In response to Re: Summary and Plan for Hot Standby  (Tatsuo Ishii <ishii@sraoss.co.jp>)
Responses Re: Summary and Plan for Hot Standby
List 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  │ trelation   │    11564 │    16384 │      │       │            │     │       │       │          │ 2/4
              │ 10449 │
 
RowExclusiveLock │ tvirtualxid │          │          │      │       │ 1/1        │     │       │       │          │ 1/0
              │ 10419 │ ExclusiveLock  │ tvirtualxid │          │          │      │       │ 2/4        │     │       │
    │          │ 2/4                │ 10449 │ ExclusiveLock  │ t
 
(4 rows)

this is from a standby.

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


pgsql-hackers by date:

Previous
From: Andrew Gierth
Date:
Subject: Re: add more frame types in window functions (ROWS)
Next
From: Peter Eisentraut
Date:
Subject: Re: Python 3.1 support