Re: Hot Standby (v9d) - Mailing list pgsql-hackers

From Gregory Stark
Subject Re: Hot Standby (v9d)
Date
Msg-id 87zlh3iq8r.fsf@oxford.xeocode.com
Whole thread Raw
In response to Re: Hot Standby (v9d)  (Hannu Krosing <hannu@krosing.net>)
Responses Re: Hot Standby (v9d)
List pgsql-hackers
Hannu Krosing <hannu@krosing.net> writes:

> Actually we came up with a solution to this - use filesystem level
> snapshots (like LVM2+XFS or ZFS), and redirect backends with
> long-running queries to use fs snapshot mounted to a different
> mountpoint.

Uhm, how do you determine which snapshot to direct the backend to? There could
have been several generations of tuples in that tid since your query started.
Do you take a snapshot every time there's a vacuum-snapshot conflict and
record which snapshot goes with that snapshot?

--  Gregory Stark EnterpriseDB          http://www.enterprisedb.com Get trained by Bruce Momjian - ask me about
EnterpriseDB'sPostgreSQL training!
 


pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: Hot Standby (v9d)
Next
From: Robert Haas
Date:
Subject: Re: Hot Standby (v9d)