From: Tom Lane <tgl@sss.pgh.pa.us>
To: Tim Allen <tim@proximity.com.au>
Cc: Hackers <pgsql-hackers@postgresql.org>
Cc: pgsql-admin@postgresql.org
Subject: Re: [HACKERS] Major Problem, need help! Can't run our website!
Date: Mon, 14 Nov 2005 23:02:42 -0500
Message-ID: <6105.1132027362@sss.pgh.pa.us> (raw)
In-Reply-To: <43795A96.9070500@proximity.com.au>
References: <227C7FFACEA9D9118BD600096BA5A7CA011E188B@EIBPOST>
<43795A96.9070500@proximity.com.au>
Tim Allen <tim@proximity.com.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 ...
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, tim@proximity.com.au, pgsql-hackers@postgresql.org
Subject: Re: [HACKERS] Major Problem, need help! Can't run our website!
In-Reply-To: <6105.1132027362@sss.pgh.pa.us>
References: <227C7FFACEA9D9118BD600096BA5A7CA011E188B@EIBPOST> <43795A96.9070500@proximity.com.au> <6105.1132027362@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox