| From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
|---|---|
| To: | tshipley(at)deru(dot)com |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: [ADMIN] Major Problem, need help! Can't run our website! |
| Date: | 2005-11-16 01:27:43 |
| Message-ID: | 437A8B0F.8020805@commandprompt.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin pgsql-hackers |
>
> Renaming the file sounds like an excellent design decision since the current
> name is a proven "human factor" bug.
>
I am sorry, but as soon as you look at the files it is obvious that they
are not "just" log files. If someone
is going to delete the xlog they are going to do it no matter what we
call it. Unless of course we change
the directory to pg_xlogs_do_not_ever_delete, but I doubt that would
help either.
Sincerely,
Joshua D. Drake
> ---------------------------(end of broadcast)---------------------------
> TIP 9: In versions below 8.0, the planner will ignore your desire to
> choose an index scan if your joining column's datatypes do not
> match
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Yogvinder Singh | 2005-11-16 10:45:27 | restore challenge |
| Previous Message | Tom Lane | 2005-11-16 00:25:47 | Re: ERROR: could not read block |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2005-11-16 01:45:50 | Re: server closed connection on a select query |
| Previous Message | Alvaro Herrera | 2005-11-16 01:11:21 | Re: PG_DUMP and table locking in PG7.4 |