Re: emergency outage requiring database restart - Mailing list pgsql-hackers

From Tom Lane
Subject Re: emergency outage requiring database restart
Date
Msg-id 18124.1477157910@sss.pgh.pa.us
Whole thread Raw
In response to Re: emergency outage requiring database restart  (Jim Nasby <Jim.Nasby@BlueTreble.com>)
Responses Re: emergency outage requiring database restart  (Jim Nasby <Jim.Nasby@BlueTreble.com>)
List pgsql-hackers
Jim Nasby <Jim.Nasby@BlueTreble.com> writes:
> On 10/21/16 7:43 PM, Tom Lane wrote:
>> Alvaro Herrera <alvherre@2ndquadrant.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



pgsql-hackers by date:

Previous
From: Jim Nasby
Date:
Subject: Re: emergency outage requiring database restart
Next
From: Tomas Vondra
Date:
Subject: Re: PATCH: two slab-like memory allocators