| From: | Kevin Grittner <kgrittn(at)ymail(dot)com> |
|---|---|
| To: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgreSQL(dot)org>, Andres Freund <andres(at)2ndquadrant(dot)com>, Dan Ports <drkp(at)csail(dot)mit(dot)edu> |
| Subject: | Re: SSI freezing bug |
| Date: | 2013-10-07 19:32:21 |
| Message-ID: | 1381174341.78668.YahooMailNeo@web162904.mail.bf1.yahoo.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Heikki Linnakangas <hlinnakangas(at)vmware(dot)com> wrote:
> A comment somewhere would be nice to explain why we're no longer worried
> about confusing an old tuple version with a new tuple in the same slot.
> Not sure where.
For now I counted on the commit message. Perhaps we also want to
add something to the README file?
--
Kevin Grittner
EDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kevin Grittner | 2013-10-07 19:35:21 | Re: SSI freezing bug |
| Previous Message | Andrew Dunstan | 2013-10-07 19:25:14 | Re: Patch: FORCE_NULL option for copy COPY in CSV mode |