Idea for debug/recovery snapshots

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: David Johnston <polobo(at)yahoo(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgreSQL(dot)org>
Subject: Idea for debug/recovery snapshots
Date: 2013-11-13 15:16:32
Message-ID: 20131113151632.GD24549@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-docs pgsql-hackers

On Tue, Nov 12, 2013 at 08:39:35PM -0500, Bruce Momjian wrote:
> > My specific wording is incoherent mostly because it really belongs to a
> > larger corpus that currently exists only in my head.
>
> Oh, OK, it sounds fine. The user really doesn't choose what timeline to
> see --- rather, it is the current xid at the time they take their
> snapshot and other running xids that controls that. You can control
> your transaction isolation level, but that only controls how often you
> take snapshots.

[ moved to hackers ]

Actually, it would be possible to allow snapshots that are equal to the
earliest active snapshot for the current database. I don't think it
would be useful in production, but perhaps for debugging or some
disaster recovery.

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ Everyone has their own god. +

In response to

Browse pgsql-docs by date

  From Date Subject
Next Message Bruce Momjian 2013-11-18 17:35:33 Re: seek advice about translation management
Previous Message Bruce Momjian 2013-11-13 15:14:19 Re: MVCC snapshot timing

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2013-11-13 15:26:32 Re: Add \i option to bring in the specified file as a quoted literal
Previous Message Simon Riggs 2013-11-13 15:16:30 Re: Fast insertion indexes: why no developments