| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Rod Taylor <pg(at)rbt(dot)ca> |
| Cc: | Tim Allen <tim(at)proximity(dot)com(dot)au>, Hackers <pgsql-hackers(at)postgresql(dot)org>, pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: [HACKERS] Major Problem, need help! Can't run our |
| Date: | 2005-11-15 04:48:07 |
| Message-ID: | 6494.1132030087@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin pgsql-hackers |
Rod Taylor <pg(at)rbt(dot)ca> writes:
> On Mon, 2005-11-14 at 23:02 -0500, Tom Lane wrote:
>> There's something in what you say. We'd have to rename pg_clog as well,
>> since that's even more critical than pg_xlog ...
> Rename them to pg_donttouchthis and pg_youneedthis.
:-)
On a more serious level: Tim's suggestion of "pg_wal" for pg_xlog sounds
fine to me. How about "pg_trans" for pg_clog, by analogy to the
existing pg_subtrans? Nothing else in the standard layout looks like
it's got a name that a newbie would think means discardable data.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | ITS ONT Alcazar, Jose Aguedo C | 2005-11-15 04:48:17 | Re: Major Problem, need help! Can't run our website! |
| Previous Message | Tom Lane | 2005-11-15 04:35:35 | Re: Major Problem, need help! Can't run our website! |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruno Wolff III | 2005-11-15 06:27:23 | Re: PostgreSQL roadmap for 8.2 and beyond. |
| Previous Message | Rod Taylor | 2005-11-15 04:32:14 | Re: [HACKERS] Major Problem, need help! Can't run our |