| From: | Joseph Shraibman <jks(at)selectacast(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: pg_log |
| Date: | 2001-01-17 03:24:44 |
| Message-ID: | 3A65107C.D1CCF692@selectacast.net |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Tom Lane wrote:
>
> "Oliver Elphick" <olly(at)lfix(dot)co(dot)uk> writes:
> > Developers:
> > I've seen this question several times; wouldn't it be better to rename
> > pg_log to pg_tuplestatus? Calling something ...log is asking for it
> > to be wiped.
>
> In 7.1 it'll have a numeric filename ($PGDATA/global/1269, actually)
> which should reduce the tendency for DBAs to assume there's nothing
> important in it. I regard this as one of the major advantages of
> having switched to numeric filenames ;-)
>
What are the others? Is the point of moving to numeric filenames to
discourage people mucking with the files? With the current system for
example if a backend coredumps I know to look for it in the directory of
the database. But how will I know what that is in the future?
--
Joseph Shraibman
jks(at)selectacast(dot)net
Increase signal to noise ratio. http://www.targabot.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Iwan Tutuka Pambudi | 2001-01-17 03:30:47 | >>>>> pg_dump in crontab |
| Previous Message | Ian Harding | 2001-01-17 03:24:15 | Re: date/time |