| From: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
|---|---|
| To: | daveg <daveg(at)sonic(dot)net> |
| Cc: | Greg Stark <gsstark(at)mit(dot)edu>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Re: PD_ALL_VISIBLE flag was incorrectly set happend during repeatable vacuum |
| Date: | 2011-03-08 08:55:38 |
| Message-ID: | 4D75EF0A.6000307@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin pgsql-hackers |
On 08.03.2011 10:38, daveg wrote:
> I read this to mean that it is safe to ignore this warning and that these
> databases are not at risk for data corruption or wrong results so long as
> the warning is due to oldestxmin. Please correct me if I have misunderstood.
Yes, that's correct.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gnanakumar | 2011-03-08 14:02:57 | How to get schema name in which TEMPORARY table is created? |
| Previous Message | daveg | 2011-03-08 08:49:56 | Re: Re: PD_ALL_VISIBLE flag was incorrectly set happend during repeatable vacuum |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian von Bidder | 2011-03-08 09:11:21 | Beginner question: Hacking environment? |
| Previous Message | daveg | 2011-03-08 08:49:56 | Re: Re: PD_ALL_VISIBLE flag was incorrectly set happend during repeatable vacuum |