Skip site navigation (1) Skip section navigation (2)

Re: Disabled features on Hot Standby

From: Jim Nasby <jim(at)nasby(dot)net>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Simon Riggs <simon(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Disabled features on Hot Standby
Date: 2012-01-13 15:31:13
Message-ID: B59DA2F0-40BF-4FB3-8F4D-4A9B71F75930@nasby.net (view raw or flat)
Thread:
Lists: pgsql-hackers
On Jan 13, 2012, at 8:03 AM, Robert Haas wrote:
> Or,
> we could try to lift this restriction in the special case when
> hot_standby_feedback is set, though I have a feeling that's not really
> robust - any time you lose the connection to the master, it'll lose
> your xmin holdback and possibly mark some things all-visible that
> really aren't on the standby, and then you reconnect and replay those
> WAL records and bad things happen.

Also, what happens if you started off with hot_standby_feedback turned off? New stuff won't just magically start working when you turn it on (or is that parameter settable only on restart?)

ISTM that hot standbys need some ability to store some "interim data" that is only needed by the hot standby while older transactions are running. IIRC we've seen other places where we have this problem too.

Perhaps it would be possible to keep older copies of pages around when there are older transactions running on the standby?
--
Jim C. Nasby, Database Architect                   jim(at)nasby(dot)net
512.569.9461 (cell)                         http://jim.nasby.net



In response to

Responses

pgsql-hackers by date

Next:From: Peter GeogheganDate: 2012-01-13 15:31:19
Subject: Re: show Heap Fetches in EXPLAIN for index-only scans
Previous:From: Magnus HaganderDate: 2012-01-13 15:29:28
Subject: Re: show Heap Fetches in EXPLAIN for index-only scans

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group