| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>,Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(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 19:02:21 |
| Message-ID: | F003382B-9E58-4529-8AD7-C95DE6FB0BFF@anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On October 22, 2016 11:59:15 AM PDT, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> writes:
>> Uh, sorry. My proposal a couple of years back was to put the
>> relfilenode, not the name. I didn't notice that it was the name
>being
>> proposed here. However, now I notice that this idea doesn't solve
>the
>> problem for mapped relations.
>
>Well, as long as a catalog lookup would be required anyway, what about
>putting in the table OID?
How about storing two table names? The old and what the relation is being renamed to? We wouldn't be able to tell after a crash which is which, but that'll usually still be helpful. Every rename would clear out the old/wrong one, and add the target filename.
Andres
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2016-10-22 19:11:01 | Re: On conflict update & hint bits |
| Previous Message | Tom Lane | 2016-10-22 18:59:15 | Re: emergency outage requiring database restart |