pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
Re: [HACKERS] Major Problem, need help! Can't run our
3+ messages / 3 participants
[nested] [flat]

* Re: [HACKERS] Major Problem, need help! Can't run our
@ 2005-11-15 04:32  Rod Taylor <pg@rbt.ca>
  0 siblings, 1 reply; 3+ messages in thread

From: Rod Taylor @ 2005-11-15 04:32 UTC (permalink / raw)
  To: Tom Lane <tgl@sss.pgh.pa.us>; +Cc: Tim Allen <tim@proximity.com.au>; Hackers <pgsql-hackers@postgresql.org>; pgsql-admin

On Mon, 2005-11-14 at 23:02 -0500, Tom Lane wrote:
> 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 ...

Rename them to pg_donttouchthis and pg_youneedthis.
-- 




^ permalink  raw  reply  [nested|flat] 3+ messages in thread

* Re: [HACKERS] Major Problem, need help! Can't run our
@ 2005-11-15 04:48  Tom Lane <tgl@sss.pgh.pa.us>
  parent: Rod Taylor <pg@rbt.ca>
  0 siblings, 1 reply; 3+ messages in thread

From: Tom Lane @ 2005-11-15 04:48 UTC (permalink / raw)
  To: Rod Taylor <pg@rbt.ca>; +Cc: Tim Allen <tim@proximity.com.au>; Hackers <pgsql-hackers@postgresql.org>; pgsql-admin

Rod Taylor <pg@rbt.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



^ permalink  raw  reply  [nested|flat] 3+ messages in thread

* Re: [HACKERS] Major Problem, need help! Can't run our
@ 2005-11-15 06:28  Jonah H. Harris <jonah.harris@gmail.com>
  parent: Tom Lane <tgl@sss.pgh.pa.us>
  0 siblings, 0 replies; 3+ messages in thread

From: Jonah H. Harris @ 2005-11-15 06:28 UTC (permalink / raw)
  To: Tom Lane <tgl@sss.pgh.pa.us>; +Cc: Rod Taylor <pg@rbt.ca>; Tim Allen <tim@proximity.com.au>; Hackers <pgsql-hackers@postgresql.org>; pgsql-admin

I agree.
 (sorry again Tom... dang GMAIL should default reply to all.... grrrr!)
 On 11/14/05, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>
> Rod Taylor <pg@rbt.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
>
> ---------------------------(end of broadcast)---------------------------
> TIP 3: Have you checked our extensive FAQ?
>
> http://www.postgresql.org/docs/faq
>

^ permalink  raw  reply  [nested|flat] 3+ messages in thread


end of thread, other threads:[~2005-11-15 06:28 UTC | newest]

Thread overview: 3+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2005-11-15 04:32 Re: [HACKERS] Major Problem, need help! Can't run our Rod Taylor <pg@rbt.ca>
2005-11-15 04:48 ` Tom Lane <tgl@sss.pgh.pa.us>
2005-11-15 06:28   ` Jonah H. Harris <jonah.harris@gmail.com>

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