| From: | Kevin Grittner <kgrittn(at)ymail(dot)com> |
|---|---|
| To: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>, Andres Freund <andres(at)2ndquadrant(dot)com> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgreSQL(dot)org>, Dan Ports <drkp(at)csail(dot)mit(dot)edu> |
| Subject: | Re: SSI freezing bug |
| Date: | 2013-10-07 14:16:08 |
| Message-ID: | 1381155368.4756.YahooMailNeo@web162906.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:
> Well, it's fairly harsh if the feature isn't working as
> advertised.
Right -- there are people counting on serializable transaction to
avoid data corruption (creation of data which violates the business
rules which they believe are being enforced). A tuple freeze at
the wrong moment could currently break that. The patch allows the
guarantee to hold. The fact that this bug is only seen if there is
a very-long-running transaction or if VACUUM FREEZE is run while
data-modifying transactions are active does not eliminate the fact
that without this patch data can be corrupted.
--
Kevin Grittner
EDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2013-10-07 14:22:10 | Re: ToDo: fast update of arrays with fixed length fields for PL/pgSQL |
| Previous Message | Andres Freund | 2013-10-07 14:14:15 | Re: SSI freezing bug |