From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Kevin Grittner <kgrittn(at)ymail(dot)com> |
Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Noah Misch <noah(at)leadboat(dot)com>, "pgsql-hackers(at)postgreSQL(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Remaining beta blockers |
Date: | 2013-05-03 00:12:32 |
Message-ID: | 20130503001232.GE5933@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, May 2, 2013 at 02:20:15PM -0700, Kevin Grittner wrote:
> > Yes, pg_upgrade is never going to write to data pages as that
> > would be slow and prevent the ability to roll back to the
> > previous cluster on error.
>
> The only person who has suggested anything which would require that
> is Andres, who suggests adding a metadata page to the front of the
> heap to store information on whether the matview is populated. I
> think it is the direct opposite of what Tom is suggesting, and has
> too many issues to be considered at this time.
>
> Nobody has proposed how the technique currently used creates a
> pg_upgrade hazard now or in some future release where we provide a
> way for recovery to put the information into the catalog. I have
> gone into more detail on this earlier on this thread.
I was more thinking of the idea of having some status on the first page
that might need to change in a future release.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2013-05-03 00:54:15 | Re: Recovery target 'immediate' |
Previous Message | Bruce Momjian | 2013-05-02 23:56:27 | Re: Recovery target 'immediate' |