From: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> |
---|---|
To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Meel Velliste <meel(dot)velliste(at)gmail(dot)com> |
Cc: | Postgres General <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Using xmax to detect deleted rows |
Date: | 2016-01-11 02:17:38 |
Message-ID: | 569310C2.7070005@BlueTreble.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 1/8/16 9:02 AM, Alvaro Herrera wrote:
> Meel Velliste wrote:
>> I would like to use the "xmax" column to detect rows that have been
>> recently deleted. Is it possible to get the deleted row versions with
>> non-zero xmax to remain visible long enough that I could periodically
>> check, say once an hour, and still be able to see rows that were deleted
>> since I last checked?
>
> No. Maybe you want a trigger that saves the deleted row somewhere (a
> separate table perhaps) which you can later inspect and delete again?
If that is what you need then PgQ might be a good solution. But it'll be
a lot simpler to just do whatever you need to do when the row is
actually deleted. Just be sure you deal with rollbacks correctly if
you're doing something external.
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com
From | Date | Subject | |
---|---|---|---|
Next Message | Jim Nasby | 2016-01-11 02:56:06 | Re: Trigger function interface |
Previous Message | Andrew Sullivan | 2016-01-11 02:00:11 | Things to notice (was Re: Code of Conduct: Is it time?, broken thread I hope) |