From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com> |
Cc: | Rick Turner <rnturn(at)baxter(dot)com>, pgsql-admin(at)postgresql(dot)org |
Subject: | Re: Database subdirectories in V7.1.x |
Date: | 2001-10-17 04:14:06 |
Message-ID: | 25134.1003292046@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com> writes:
> The reason tables got renamed into numbers was due to rollbacks of
> drops or drops followed by creates in the same transaction.
That was one reason, but an equally big reason was to have a compact way
of referencing tables in the WAL logs, such that a process re-applying
changes during crash recovery wouldn't need any outside info to apply
the changes. Database and table OIDs fit that description, names do
not.
> I assume that the plan was to move databases in the same direction
I don't think that there are any plans to make DROP DATABASE
rollback-able, but the WAL recovery issue is sufficient reason to use
database OIDs for directory names.
The short answer is that this design decision will not be reversed...
learn about oid2name if you feel a need to understand the substructure
of $PGDATA.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Stephan Szabo | 2001-10-17 04:45:26 | Re: ALTER TABLE commands |
Previous Message | Tariq Muhammad | 2001-10-17 03:43:03 | ALTER TABLE commands |