| From: | Kevin Grittner <kgrittn(at)ymail(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)2ndquadrant(dot)com> |
| Cc: | Dan Ports <drkp(at)csail(dot)mit(dot)edu>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: MultiXact bugs |
| Date: | 2013-11-29 22:00:09 |
| Message-ID: | 1385762409.39602.YahooMailNeo@web162905.mail.bf1.yahoo.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Andres Freund <andres(at)2ndquadrant(dot)com> wrote:
> Looking at predicate.c I think I see a bigger problem though: Isn't its
> usage of HeapTupleSatisfiesVacuum() quite dangerous? It passes
> TransactionXmin to HeapTupleSatisfiesVacuum(). But since that's just the
> transaction's own cutoff, not the global cutoff that will cause wrong
> hint bits to be set. Or am I missing something?
I don't see where that parameter has anything to do with setting
hint bits; it only seems to affect the return code for the caller.
--
Kevin Grittner
EDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeffrey Walton | 2013-11-29 23:01:01 | Re: fe-secure.c and SSL/TLS |
| Previous Message | Tom Lane | 2013-11-29 21:48:13 | Re: [RFC] overflow checks optimized away |