| From: | "Kevin Grittner" <kgrittn(at)mail(dot)com> |
|---|---|
| To: | "Alejandro Carrillo" <fasterzip(at)yahoo(dot)es>,"Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: not(t_xmax = 0) |
| Date: | 2013-01-21 16:10:55 |
| Message-ID: | 20130121161055.120600@gmx.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Alejandro Carrillo wrote:
> this function didn't work to know if a row can surely dead?
>
> http://doxygen.postgresql.org/tqual_8c_source.html#l01236
Sure, as long as you call it after HeapTupleSatisfiesMVCC(), as the
comment specifies. Also note that not all deleted or updated tuples
will be retained for very long; HOT pruning and autovacuum can
clean up dead tuples at unpredictable times. But if you want to
know which among the old tuples that are still in the heap will go
away when the next vacuum against the table runs, that would be one
way to do it.
-Kevin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | bhanu udaya | 2013-01-21 16:15:32 | Re: pg_Restore |
| Previous Message | Alan Hodgson | 2013-01-21 16:10:16 | Re: pg_Restore |