Skip site navigation (1) Skip section navigation (2)

Re: Thanks, naming conventions, and count()

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Vince Vielhaber <vev(at)michvhf(dot)com>
Cc: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, The Hermit Hacker <scrappy(at)hub(dot)org>, Casey Lyon <casey(at)earthcars(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Thanks, naming conventions, and count()
Date: 2001-04-30 15:44:36
Message-ID: 15231.988645476@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackers
Vince Vielhaber <vev(at)michvhf(dot)com> writes:
>> Oh, you did a direct postgres backend connect.  Yes, that will work
>> fine.  Good idea if the postmaster is down.  I originally thought you
>> meant reading the pg_class file raw.  Of course, that would be really
>> hard because there is no way to know what numeric file is pg_class!

> But would it work on a crashed database that won't come up

No.

It's not that hard to know "which numeric file is pg_class" --- that
info has to be hard-wired in at some level.  (The backends cannot learn
pg_class's own relfilenode number by examining its pg_class entry...)

It might be worth making a simple utility (could be based on Bryan
White's pg_check) to grovel through the raw pg_class bits and extract
relfilenode info the hard way.  You'd only need it in certain disaster
scenarios, but when you did need it you'd need it bad.

So far we have not seen a report of a situation where this seemed to be
useful, so I'm not that excited about having it... WAL dump and
interrogation utilities are higher on my want list.

			regards, tom lane

In response to

Responses

pgsql-hackers by date

Next:From: Bruce MomjianDate: 2001-04-30 15:56:38
Subject: Re: Thanks, naming conventions, and count()
Previous:From: Tom LaneDate: 2001-04-30 15:36:58
Subject: Re: COPY commands could use an enhancement.

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group