| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> |
| Cc: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Merlin Moncure <mmoncure(at)gmail(dot)com>, Kevin Grittner <kgrittn(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: emergency outage requiring database restart |
| Date: | 2016-10-22 17:38:30 |
| Message-ID: | 18124.1477157910@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> writes:
> On 10/21/16 7:43 PM, Tom Lane wrote:
>> Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> writes:
>>> Agreed. The problem is how to install it without breaking pg_upgrade.
> It can't look up relation names?
It can't shove 64 bytes into a page that has < 64 bytes free space.
>> Well, that's the first problem. The second problem is how to cope with
>> RENAME TABLE.
> If the name was only encoded in the first block of the relation I'm not
> sure how bad this would be; are there any facilities to change the name
> back on a rollback?
No. How would that work in crash situations? (And keep in mind that the
argument for this hinges entirely on its being 100% trustworthy after a
crash.)
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tomas Vondra | 2016-10-22 18:30:41 | Re: PATCH: two slab-like memory allocators |
| Previous Message | Jim Nasby | 2016-10-22 17:13:06 | Re: emergency outage requiring database restart |