| From: | Rod Taylor <pg(at)rbt(dot)ca> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| 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:32:14 |
| Message-ID: | 1132029134.7495.88.camel@home |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin pgsql-hackers |
On Mon, 2005-11-14 at 23:02 -0500, Tom Lane wrote:
> Tim Allen <tim(at)proximity(dot)com(dot)au> writes:
> > We've seen reports of people firing this particular foot-gun before,
> > haven't we? Would it make sense to rename pg_xlog to something that
> > doesn't sound like it's "just" full of log files? Eg pg_wal - something
> > where the half-educated will have no idea what it is, and therefore not
> > think they know what they can do with it.
>
> 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.
--
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2005-11-15 04:35:35 | Re: Major Problem, need help! Can't run our website! |
| Previous Message | Tom Lane | 2005-11-15 04:17:58 | Re: [HACKERS] Major Problem, need help! Can't run our website! |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2005-11-15 04:48:07 | Re: [HACKERS] Major Problem, need help! Can't run our |
| Previous Message | Tom Lane | 2005-11-15 04:17:58 | Re: [HACKERS] Major Problem, need help! Can't run our website! |