Is there something similar like flashback query from Oracle planned for PostgreSQL

Started by Dirk Krautschickalmost 5 years ago3 messagesgeneral
Jump to latest
#1Dirk Krautschick
Dirk.Krautschick@trivadis.com

Hi,

just a curious question...

Is there something planned to get a behaviour like Oracle's flashback query based on the old values
before deleted by vacuum?

So a feature to recreate old versions of rows if still there?

Or are there any related extensions or tools doing this?

Thanks

Dirk

#2Vijaykumar Jain
vijaykumarjain.github@gmail.com
In reply to: Dirk Krautschick (#1)
Re: Is there something similar like flashback query from Oracle planned for PostgreSQL

On Thu, 24 Jun 2021 at 00:24, Dirk Krautschick <
Dirk.Krautschick@trivadis.com> wrote:

Hi,
Is there something planned to get a behaviour like Oracle's flashback
query based on the old values
before deleted by vacuum?

So a feature to recreate old versions of rows if still there?

Or are there any related extensions or tools doing this?

postgresql has external tools like barman that ship WALs to a different
location for point in time recovery.
That way, you can restore the db to any point in the past since the time
you were collecting WALs.

Barman Manual (pgbarman.org) <http://docs.pgbarman.org/release/2.12/&gt;
if this is not the same, then please ignore the above :)

--
Thanks,
Vijay
Mumbai, India

#3Thomas Munro
thomas.munro@gmail.com
In reply to: Dirk Krautschick (#1)
Re: Is there something similar like flashback query from Oracle planned for PostgreSQL

On Thu, Jun 24, 2021 at 6:54 AM Dirk Krautschick
<Dirk.Krautschick@trivadis.com> wrote:

Is there something planned to get a behaviour like Oracle's flashback query based on the old values
before deleted by vacuum?

So a feature to recreate old versions of rows if still there?

Or are there any related extensions or tools doing this?

There are some things like pg_dirtyread and probably more. You might
be interested in some of the references in this thread:

/messages/by-id/CAKLmikOkK+s0V+3Pi1vS2GUWQ0FAj8fEkVj9WTGSwZE9nRsCbQ@mail.gmail.com

As for the SQL standard's approach to this, there are some active
-hackers threads on that with patches in development... look for
"temporal tables" and "system versioned".