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

From Jim Nasby
Subject Re: emergency outage requiring database restart
Date
Msg-id 16162ffe-ae5c-772d-8bd4-aacbf864f1e7@BlueTreble.com
Whole thread Raw
In response to Re: emergency outage requiring database restart  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: emergency outage requiring database restart  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On 10/21/16 7:43 PM, Tom Lane wrote:
> Alvaro Herrera <alvherre@2ndquadrant.com> writes:
>> Jim Nasby wrote:
>>> It occurs to me that it might be worth embedding the relation name in the
>>> free space of the first block. Most people would never notice the missing 64
>>> bytes, but it would be incredibly helpful in cases like this...
>
>> Agreed.  The problem is how to install it without breaking pg_upgrade.

It can't look up relation names?

> 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?
-- 
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com
855-TREBLE2 (855-873-2532)   mobile: 512-569-9461



pgsql-hackers by date:

Previous
From: Ashutosh Bapat
Date:
Subject: Re: Push down more full joins in postgres_fdw
Next
From: Tom Lane
Date:
Subject: Re: emergency outage requiring database restart